How it works

Four steps, running continuously.

Manuel runs as work arrives, so exceptions appear when they happen.

Step 1. Read

Pulls documents and data from wherever they arrive: email, portals, scans, SFTP, ERP tables, bank files. Extraction is contextual, so a new supplier format is not a new project.

One PDF may contain several invoices, and one invoice may span many pages. Manuel splits, classifies, and assembles each business record. It keeps the source location for every extracted value.

Step 2. Check

Triangulates each item against the records that should agree with it: the purchase order, the goods receipt, the contract, the rate table, the bank statement, the delivery record.

Matching uses ordered rules, fallbacks, tolerances, date windows, and relationships. Manuel stores these settings as configuration so the team can update them.

Step 3. Decide

Clean items pass. Items with a mismatch are held for review with the reason clearly named.

A useful finding states that the unit price is 4.2 percent above the contracted rate on lines 3 and 7 and identifies the contract version approved on 12 March. The reviewer can act without repeating the investigation.

Step 4. Act

Posts, files, notifies, updates, routes for approval. Every step leaves a record of what was checked and against what.

Manuel can write back to an approved system or produce a file, journal, or approval request for your team. Most first deployments start in read-only mode.

Works with the systems you already use.

Core systems execute and record transactions. Checking the result can require a bank statement, processor file, contract, master data, and ledger at the same time.

Manuel brings those records together for the check. Your systems of record stay in place.

• Versioned rules
• Works with your systems
• Shared across controls

Describe the result you expect. Manuel runs the steps.

The difference is easiest to see in a simple matching rule.

In a workflow builder you draw this

clean to join to filter to loop unmatched to fuzzy match to route to notify

And then you maintain it. Every time the business changes a tolerance, someone opens the canvas.

In Manuel you write this

Match by Settlement ID first. If unmatched, use Merchant plus Amount plus Date within one day. Variance above the approved tolerance becomes an exception.

Match supplier using Tax ID first, supplier name as fallback, then return Supplier ID and Payment Terms.

The person who understands the operation can state and update the rule without rebuilding the process.

Manuel handles document intake, entity matching, calculations, checks, and exception review in the background.

Change a business rule without rebuilding the software.

Six modules run on one shared platform.

Every new control reuses the same six modules. Only the rules and the data mappings change.