How InvoiceGap works

From your documents to findings you can check.

Choose what to check, add your records, and review invoices, deliveries, credit notes and payments together. InvoiceGap shows which differences the documents support, what remains unclear and what to check next.

Expected £100,000 Amount due under the applicable commercial terms
↓
Recognized £92,000 Amount remaining after supported commercial adjustments
↓
Paid £87,000 Amount actually received and applied

Why simple matching is not enough

A matched payment does not always explain the outstanding balance.

In B2B trade, a correctly issued invoice can still result in a materially different settlement after subsequent commercial or operational adjustments.

A shipment may arrive short. Part of the delivery may be rejected. A buyer may issue a claim. A credit note may be valid — or may refer to the wrong transaction. A payment may cover several invoices, or only part of the amount the buyer already recognized.

Looking only at the invoice and payment may identify a variance without explaining its underlying cause. It does not always show why.

InvoiceGap helps financial control trace that variance across the relevant commercial, operational and financial records.

Follow the transaction from commercial terms to payment

A receivables variance can originate well before payment.

The documents vary by industry, but a receivables variance may originate at several stages before it appears as an outstanding financial balance.

Contract → Order → Shipment → Delivery → Accepted quantity → Claim / return → Credit / debit → Invoice → Remittance → Payment

The InvoiceGap model

Three financial states make the variance easier to explain.

Instead of compressing every difference into one unexplained outstanding balance, InvoiceGap keeps three separate financial states.

01 — Expected

What amount is commercially due?

Expected represents the amount supported by the applicable commercial terms and transaction records. Depending on the business, that can include contract pricing, relevant quantities, agreed adjustments and other supported commercial terms.

The objective is not to estimate what an invoice “probably should be.” It is to establish a supportable financial starting point from the available records.

02 — Recognized

What amount is commercially recognized after adjustments?

Recognized keeps legitimate commercial adjustments separate from the payment itself.

A valid credit, deduction, claim or other supported adjustment may change the amount that remains commercially due. That change belongs here — not inside the payment number.

03 — Paid

What amount was actually received and applied?

Paid reflects the amount actually applied through payment or remittance evidence.

Keeping Paid separate means a short payment cannot silently rewrite the commercial explanation that came before it.

Two variances. Two different questions.

Separate commercial adjustments from settlement variances.

Separating the two variances gives financial control a clearer basis for investigation, resolution and action.

Expected → Recognized

What changed commercially?

This is where InvoiceGap identifies the supported commercial explanation: quantity differences, delivery issues, returns, claims, pricing adjustments, credit notes or other relevant events.

Recognized → Paid

What remains financially unsettled?

This is the settlement question: short payment, partial payment, unapplied cash, incorrect allocation, or an amount that still has no supporting explanation.

Illustrative example

One £13,000 variance. Two different financial explanations.

This example is illustrative and is not presented as a customer result.

Commercial expectation £100,000 Supported starting amount
− £8,000

Supported delivery shortage and credit

Recognized amount £92,000 Commercially supported after adjustment
− £5,000

Payment difference with no supporting adjustment found

Paid £87,000 Actual settlement
Commercially explained £8,000
Unresolved variance £5,000

Five steps, from files to a decision

Review a discrepancy without changing your accounting system.

Your team chooses the scope and stays in control of the final decisions.

01

Choose what you want to check

Check all supported discrepancies or focus on delivery quantities, claims, pricing adjustments or payments. Narrow the review by buyer and period when useful.

02

Add the records

Upload invoices, orders, delivery documents, credit notes, remittances and payment evidence, or select files already in your workspace.

03

Review the differences

InvoiceGap compares linked transactions where the evidence is sufficient. Commercial adjustments and payment differences are shown separately.

04

Check the supporting evidence

See what the records support, which documents are missing and which connections still need human review. Missing evidence never means there is no discrepancy.

05

Decide what to do next

Review open cases and reports, record decisions and choose the next action. Your team remains responsible for accounting, legal and commercial decisions.

When the evidence is not certain

Uncertainty should remain visible until the evidence supports a conclusion.

Business records are often incomplete. References can conflict. Several deliveries may relate to one invoice. Two contracts may overlap. A document may suggest a reason without proving it.

Where the available records do not support a reliable conclusion, InvoiceGap keeps the ambiguity visible for review and separates uncertain evidence from confirmed financial conclusions.

Human review remains part of the workflow where judgement is required.

For financial control

A clearer basis for financial control and exception resolution.

Reconciliation view

Expected, Recognized and Paid

See the three financial states separately instead of hiding them inside a single balance.

Variance explanation

What explains the variance

Understand whether the difference appears commercial, physical, financial or still unresolved.

Evidence

Records supporting the case

Keep the explanation connected to the relevant source documents and transaction evidence.

Action

What needs to happen next

Support financial control by focusing review on the cases that require recovery, escalation, further investigation or closure.

COMMON TRADE DISCREPANCIES

Short Payments, Buyer Deductions and Trade Discrepancies

Delivery shortages and quantity differences

Short shipments and differences between ordered, shipped, delivered and accepted quantities.

Goods damage, quality claims and returns

Reported damage, rejected or returned quantities, and customer quality complaints.

Pricing and commercial adjustments

Invoice pricing differences, agreed discounts and linked credit notes.

Buyer deductions and disputed amounts

Customer-recorded deductions, claims and adjustments requiring supporting documents.

Payments and remittances

Partial payments, unmatched allocations, overdue invoices and outstanding balances.

No ERP project required

Keep your ERP. Use InvoiceGap alongside it.

Your ERP remains your system of record. InvoiceGap works with the files you choose to upload.

No need to:

  • give InvoiceGap direct access to SAP, Dynamics or NetSuite;
  • share ERP usernames or passwords;
  • open an API connection just to get started;
  • provide direct access to your bank account;
  • set up two-way synchronisation;
  • involve your IT team in a large integration project;
  • allow an external system to write data back into your ERP.

Start with the files you already use.

Upload Excel, CSV, PDF, ERP exports, bank statements and shipping documents. Review them together with your finance team, or use the results for management review.

See the workflow on your data

Start with a limited reconciliation scan.

Start free scan