By Artem Korsakov ·
Supplier invoice reconciliation is required before passing the document for payment. The amount may look familiar, although the price has changed, part of the goods has not yet arrived, shipping was calculated twice, or the same invoice was sent again. AI helps transfer lines from PDF and email into a verifiable table. Next, comparison rules, contract terms, and the decision of the responsible employee come into play.
Three documents answer different questions
The order shows what and under what conditions the company agreed to purchase. The receipt shows what was actually received and accepted. The invoice states what the supplier asks to be paid for. A match of total amounts does not mean a match in composition, quantity, or basis. Therefore, reconciliation at the line and related batch level is useful.
The Dynamics 365 documentation describes three-way matching: the invoice is matched with the order and receipt details, applying agreed rules. The link shows the approach itself; purchasing Dynamics for it is not required. A limited version can be implemented on top of current accounting, if the necessary data is available.
At the same time, not every payment requires prior receipt. Advance payments, milestone payments, rent, and services have their own basis. You cannot mechanically apply the rule “goods not received, do not pay” to them. The card indicates the type of obligation, stage, and agreed procedure. The first version may cover only standard supplies with payment after receipt.
Where to get data if 1C (a Russian accounting and ERP platform) and Excel are already in use
First, check if there is an order, receipt, and settlements in the existing configuration. 1C:ERP supports managing settlements by settlement objects. Creating a second independent accounting for payments may add discrepancies instead of control. The additional service only needs confirmed data and a link to the source document.
If procurement manages the order in Excel, and the warehouse accepts goods in 1C, a stable order number and line correspondence are required. The file name and procurement officer's surname are insufficient for this. In a pilot, loading approved exports is permissible: it is important to record the time, period, organization, and author. Missing receipt export is shown as a data deficiency. It does not serve as proof that the delivery did not happen.
Before connecting, discuss who corrects each error. The supplier clarifies their document, the procurement officer confirms the order change, the warehouse adjusts receipt details, and accounting checks settlements. The service collects a queue of discrepancies and history, but does not rewrite documents for these departments.
How invoice recognition with AI works
Invoice recognition with AI starts with the original file. The output needs the supplier, buyer organization, number and date, currency, tax details, lines, units, quantities, prices, and total. Each critical value must be open next to the source. If the file contains multiple invoices or attachments, their separation is checked before comparison.
The AI Builder documentation describes extracting fields of an invoice, recognized text, and page number. Confidence scoring helps distribute verification, but does not prove the correctness of the amount. A specific model is chosen based on your formats, language, processing conditions, and availability. The presence of a function in the documentation of an international platform does not mean it suits your company.
AI also suggests line matching: “power cable” in the invoice and a specific article number in the order. If characteristics are insufficient, the line remains unmatched. Name similarity does not confirm brand, cross-section, product variant, or whether substitution is acceptable. Technical equivalence is confirmed by a competent employee.
Подпись: Illustrative example. A line without cable cross-section remains unmatched. Comparison with the order and receipt follows rules.
What rules check after recognition
Invoice and order reconciliation includes organization, currency, article number, characteristics, unit, price, quantity, and agreed additional expenses. Line arithmetic and total are checked separately. Tax conditions and rounding rules are taken from documents and company settings. Model assumptions are not used here.
The next level links quantity with receipt details and previous documents for this supply. If sixty of one hundred units are accepted, a new invoice for the remaining forty cannot be considered a duplicate solely due to the same order. Conversely, two different PDFs may relate to one obligation. The service must show a history of partial deliveries and previously reviewed invoices.
Tolerance for rounding is set separately from permission to change the price. A small rounding difference and an unplanned tariff increase have different reasons. A universal percentage at which “everything is automatically normal” is dangerous for expensive items. Even a small relative deviation can be a significant amount.
Educational example with partial receipt
The order contains 100 units at 1,000 rubles, totaling 100,000 rubles. For simplicity, all amounts in the example are on a single tax basis, without shipping. The first batch contains 60 units, but two are damaged and not accepted. Confirmed receipt amounts to 58 units. The supplier issues an invoice for 60 units at 1,050 rubles, totaling 63,000 rubles.
The service shows two independent discrepancies. The price has risen by 50 rubles per unit relative to the order. The payable quantity exceeds confirmed receipt by two units, if for this delivery payment of accepted goods applies. The cost of 58 accepted units at the agreed price is 58,000 rubles. The difference with the invoice is 5,000 rubles: 3,000 due to price on all 60 line units and 2,000 due to two unaccepted units at the base price.
This breakdown explains the discrepancy, but does not automatically set the payment amount. There may have been an agreed price change or other calculation procedure. The responsible party attaches a basis or requests a corrected invoice. After resolution, the system stores the source document, confirmed version, and decision author.
Подпись: Illustrative example on a single tax basis, without shipping. The 5,000 ruble difference consists of price increase and two unaccepted units. Payment amount is decided by the responsible employee.
How to search for potential duplicates
The first level of verification compares the file as a whole: re-uploading the same attachment should not create a new card. The second matches supplier, organization, number, date, currency, and amount. The third shows similar documents where the number is recorded differently or the date has changed. Such matches are only candidates for verification; a duplicate is not yet proven.
A corrected invoice may have the same number but different composition. It is linked to the previous version; it cannot be deleted. Regular services may yield identical amounts every month; the period is crucial here. An invoice and receipt document are also not two separate obligations simply because both contain cost.
Automation of invoice verification reduces the risk of missing such situations with correct data, but does not guarantee protection against fraud. Changing bank details requires separate verification according to the company's accepted procedure. Line matching and confident recognition do not confirm the authenticity of the sender or payment basis.
What the approver's workspace looks like
The employee opens a list of documents awaiting decision. The card shows the source invoice, order lines, and confirmed receipt side by side. Reasons are highlighted specifically: “order not found”, “unit not matched”, “price differs”, “looks like previous version”. Instead of a general red banner, there is an action and responsible party.
Decisions may be: request clarification, accept confirmed change, route for additional approval, mark document as replaced. The reason and attachment are saved in the journal. “Verified” status is not equal to “paid”. Payment fact comes from an approved source and links to the obligation, so that re-review does not trigger a second payment.
Before passing for payment, check if the order or receipt changed after approval. If the source version became different, comparison results are outdated. The system re-shows discrepancies; green status from yesterday's version does not persist.
How to limit the first version
Start with one organization, one currency, and a clear procurement category. Include several suppliers with recurring document formats. The first version may prepare a discrepancy registry and approved file for further work, without creating payment orders or posting documents in accounting.
Verification must include partial delivery, corrected invoice, duplicate attachment, different unit, additional shipping, and missing receipt. Count the time for full review, number of false alarms, and missed known discrepancies. Demonstration on one clean PDF does not check process operation.
To discuss such a product, prepare an anonymized set: order, invoice, receipt, and example correction. trike_dev will help design a verifiable route and a small approval portal that complements existing systems.
Related reading: Comparing supplier quotes with AI for construction procurement; Data preparation for automation: catalogs without confusion.
Частые вопросы ### Can matched invoices be paid automatically?
Data match itself does not grant the right to payment. First, you must check basis, access, document relevance, and company rules. In the initial launch, it is more useful to limit yourself to preparing the reconciliation result for the employee.
What if there is no structured order?
You can start with an approved table containing order number, lines, units, and prices. If agreements remain only in calls, they first need to be recorded. AI will not restore reliable conditions from missing documents.