Touchless AP in wholesale distribution: processing 1,000 invoices/month without losing margin

Wholesale distribution is a volume and thin-margin business. Whoever sells hardware to local stores, food to hospitality, school supplies to schools or healthcare equipment to clinics moves thousands of SKUs and hundreds of suppliers with typical gross margins of 2-5%. A poorly managed margin point on purchases turns directly into lost EBITDA.

A mid-sized distributor's AP processes between 800 and 1,200 invoices per month. Most are recurring, with volume discounts, quarterly or annual rebates, partial deliveries and constant returns. Manual AP does not scale. And, worse, semi-manual AP with a generic OCR that does not understand lines does not scale either: it detects the header total and lets through the real line-level deviations.

This article is for whoever runs administration or procurement at a Spanish SME distributor and is tired of finding out late that margin has slipped away through price increases nobody noticed. Thesis: touchless AP in distribution does work, but only if the system cross-checks line by line against the purchase order and delivery note, and handles rebate credit notes separately from the invoice.

Why wholesale distribution is different from the rest of AP

According to interior commerce data published by INE and sector benchmarks compiled by AECOC (Spanish Commercial Coding Association), wholesale commerce moves very high volume with compressed margins. What is relevant for AP is cost composition: 75-90% of a distributor's total cost is cost of goods, bought from 100-300 suppliers with daily or weekly frequency.

The five traits that make this case different:

• High and dispersed volume. 800-1,200 invoices/month in a distributor with two or three branches is usual. Each branch receives daily deliveries and each supplier invoices on their own pace: weekly, fortnightly, monthly.
• 2-5% margins on sales. No cushion. A 1.5% price rise on a high-rotation SKU not detected eats the whole margin on that SKU for the period.
• Catalogues with thousands of SKUs. A hardware distributor handles 8,000-15,000 active SKUs. The agreed price lives in an annual framework agreement with family tariff and negotiated discounts. Nobody reviews each invoice line by line.
• Constant partial deliveries. The supplier ships 60% of the PO today, 30% next week and 10% never arrives. If the invoice arrives before the complete delivery note, amounts do not reconcile and pending adjustments pile up.
• Quarterly and annual rebates. Supplier agreements include accumulated volume discounts: 2% rebate if you buy more than EUR 100,000/quarter, scaling to 3.5% above EUR 200,000. Claiming them on time is admin work many SMEs do poorly or late.

The result is that an admin team of two or three people spends 80-120 hours per month entering invoices and disputing differences, and errors still slip through. AP benchmarking figures put the average cost of manually processing an invoice at EUR 12-18 in mid-sized companies. At 1,000 invoices/month, that is EUR 12,000-18,000 per month in capture and reconciliation labour alone.

Classic problems in distribution AP

The table summarises the most frequent blockages in Spanish wholesale distribution. None is solved with classic OCR or a generic approval workflow.

Problem	Typical frequency	Margin impact
Silent price rises on recurring SKUs	3-7% of lines/quarter	Direct leak, hard to reverse
Partial deliveries billed as complete	10-20% of POs	Overpayment + later manual adjustment
Accumulated rebates unclaimed or late	20-40% of rebate suppliers	Deferred liquidity, sometimes lost
Duplicates across branches	1-3% of invoices	Double payment if not detected in time
Substituted SKUs without price adjustment	3-8% of lines	Payment for the more expensive product

Impact on margin and EBITDA

The math is brutal in its simplicity. A distributor with EUR 6M annual revenue and a 4% gross margin has EUR 240,000 of margin to cover staff, rent, logistics and finance. If undetected billing errors take between 1% and 3% of purchases — a reasonable range per sector data — the estimated leak is between EUR 50,000 and EUR 150,000/year on annual purchases of EUR 5M. That is between 20% and 60% of gross margin.

For a smaller distributor with annual purchases of EUR 1.5M, the estimated leak sits in the EUR 15,000-60,000/year range. It is still money the business owner is leaving on the table every year without seeing it in any dashboard, because it is hidden inside cost of goods sold.

The silent bias is always in the supplier's favour. When the price rises, they reflect it on the invoice without notice. When delivering partially, they invoice as complete and issue a credit note "when they can". When applying a rebate, they wait for you to claim it. This is not structural bad faith; it is information asymmetry. Touchless AP closes it from the receiver's side.

The touchless flow adapted to distribution

A generic touchless flow does not work here. Five phases must be adapted:

1. Multi-branch ingestion. Each branch or logistics centre has its own inbox or alias, and invoices from every mailbox land in the same queue without anyone forwarding anything. ininvoice does not assign a branch or cost centre; that allocation is done in the ERP.
2. OCR/IDP on invoices with multiple discounts. A typical distribution invoice includes promo discount, prompt-payment discount, family discount, all per line. The extractor must read each applied discount separately and compute the net unit price before comparing.
3. Three-way matching against the PO and partial deliveries. The real match is purchase order (with the agreed price) vs delivery note vs invoice. When there are partial deliveries, the system accumulates delivery notes linked to the PO and compares against the invoice only for lines effectively received. Tolerance is applied line by line, not on the header.
4. Who answers each exception. A price variance is a question for procurement (renegotiate). A quantity variance is one for the warehouse manager (verify what was received). A possible duplicate is one for administration. ininvoice shows the type and the reason of each exception; your team decides who follows it up, and a person approves the invoice.
5. Export to the distribution ERP. Once a person has approved them, invoices are exported as a CSV or Excel file that the ERP imports, and from there the data feeds margin dashboards by family, supplier and branch.

This flow puts humans where they add value: procurement renegotiating, warehouse verifying receipts, administration reviewing exceptions and approving invoices.

Specific tolerances by product category

One of the most misunderstood decisions is applying the same tolerance to the whole catalogue. In distribution it does not work. A box of screws does not vary; a box of fruit does.

Reasonable tolerance framework as a starting point (always line by line, never header):

• Perishable products (fresh food, frozen). Quantity tolerance 3-5% for losses and variable weight. Price tolerance stays tight.
• Durable packaged product (hardware, stationery, equipment). Quantity tolerance at most 1% (ideally zero). Units are closed and weight is exact.
• Promotional and high rotation. Price tolerance 2% or EUR 1.50 in OR mode — a line is flagged if it exceeds either limit. It is the base tolerance we recommend in three-way matching for stable high-volume SKUs.
• Low-rotation SKU with volume-step price. Zero price tolerance. If there is a difference, there is a tariff error or an unapplied step.

These numbers are a starting point for your own policy, to be reviewed with real business data. In ininvoice the tolerance is set by the organisation; the default is 2% or EUR 1.50 per line in OR mode. The universal rule: never use the same tolerance for a box of fruit and a box of light bulbs.

Rebates and volume discounts: the special case

Rebates are the block that generates the most discrepancies between billed and actually owed. They work backwards from the normal flow: the supplier bills at standard prices during the quarter and, at close, issues a credit note for the accumulated rebate. If nobody cross-checks accumulated purchases against the agreed tier table, the credit note falls short or never arrives.

Typical cases:

• Monthly rebate on monthly purchases (rare, but exists in some sectors).
• Quarterly rebate scaled by tier: 2% over EUR 50k, 3% over EUR 100k, 4% over EUR 200k.
• Annual rebate with year-end settlement. The most frequent and the easiest to lose.
• Mixed rebate with additional promo bonus by category or brand.

ininvoice does not calculate rebates or track tiers. What it does is link each rebate credit note to the invoice it cites, by invoice number and supplier tax ID, so the credit note is neither lost nor set against the wrong invoice. Checking accumulated purchases against the agreed tier table is still procurement’s job, and a person approves the credit note like any other document. Without that check, part of the agreed rebate is often lost — not because the supplier denies it, but because nobody claims it in time.

Integration with distribution ERP

AP does not live in isolation. The invoice arrives, gets reconciled and approved, and the approved data feeds the ERP that already manages stock, sales and margin. A typical distribution stack combines:

• Horizontal or vertical distribution ERP with products like Holded, Sage 50/200, Distrito K, Solmicro or sector vertical packages.
• AP automation layer between the supplier inbox and the ERP. ininvoice lives here: ingestion, reading, three-way matching, approval by a person and export of approved invoices.
• BI or dashboard on top of the ERP for margin by family, supplier and branch. The BI drinks from clean data, not from invoices with dragged-in errors.

The idea is not to duplicate masters. Suppliers and catalogue live in the ERP; ininvoice does not read them. The AP layer reads the documents, matches them and, once a person has approved, exports.

Verifactu and distribution

When food, consumer goods and wholesale suppliers start issuing with Verifactu and B2B e-invoicing, distributors will receive more invoices with structured data. They are two rules with different calendars. B2B e-invoicing (Law 18/2022, developed by Royal Decree 238/2026) applies from 6 October 2027 to companies with turnover above EUR 8 million and from 6 October 2028 to everyone else, according to the AEAT implementation calendar. Verifactu (Royal Decree 1007/2023) requires the issuer to have its billing system adapted before 1 January 2027 if it pays corporate income tax and before 1 July 2027 in all other cases, after Royal Decree-law 15/2025; businesses keeping their VAT books through the SII are outside it. On 5 October 2026 the Ministry of Finance announced a delay of Verifactu to October 2028, which for now is only an announcement. The recipient of the invoice has no Verifactu obligation.

For a distributor, the practical job does not change: every invoice received, whether it arrives as a PDF, an image or a scan, has to match its purchase order and delivery note line by line before it is paid. If the supplier uses the VERI*FACTU mode, its billing records also reach the AEAT when issued, so a divergence between your books and what the supplier invoiced is easier to spot.

Estimated case: distributor with 100 suppliers

Indicative figures for an SME distributor with 100 active suppliers, 800 invoices/month and two people dedicated to administration.

Metric	Manual AP	With ininvoice (estimate)
Hours/month on capture and reconciliation	~100 h	~25 h (exceptions only)
Average invoice → ledger time	10-15 days	<48 h
Discrepancies detected	Only what someone reviews by hand	Every matched line is checked
Imputable AP staff cost	~EUR 2,000/month	~EUR 500/month
AP software cost	EUR 0	Tailored pricing
Estimated AP staff saving (before software)	—	~EUR 1,500

This does not include recovered margin. If the distributor captures 1% leak on EUR 5M/year of purchases, that is EUR 50,000 additional typically lost in the "we do not know exactly where the margin goes".

Checklist for the procurement director

Ten concrete actions a procurement director at a distributor can kick off this quarter without touching the ERP:

1. Inventory the real volume: how many invoices/month the company receives, how many active suppliers and how many different SKUs.
2. Identify the top 20 suppliers by amount and the top 20 by invoice count. They usually do not overlap.
3. List suppliers with agreed rebate and review whether the last received credit note reconciles with real accumulated purchases.
4. Measure how much time administration spends on capture vs on discrepancy resolution. The ratio reveals the problem.
5. Audit a sample of 50 invoices from the last quarter at line price: how many have a silent rise vs agreed tariff.
6. Compute current gross margin by family and supplier. The dispersion is usually revealing.
7. Define tolerances by category (perishables, durables, promotionals) before configuring the flow.
8. Confirm with the accounting team or firm how clean data flows into the ERP (Holded, Sage, Distrito K, sector vertical).
9. Agree who answers each exception: procurement (price), warehouse (quantity), administration (possible duplicates).
10. Pilot with one branch and the top 10 suppliers before extending. Measure KPIs for 4-6 weeks.

Frequently asked questions

Does this work if my suppliers still send poorly structured PDF invoices?

Yes. The IDP engine is trained to extract lines with description, quantity, unit price and per-line discount, even if layout changes between suppliers. Structured e-invoices (XML) will be read directly; that reading is in development.

What about partial deliveries billed as they arrive?

The system accumulates the delivery notes linked to the PO and compares the invoice against the lines effectively received up to the invoice date. If the invoice bills more than has been received, the difference is flagged for a person to review before the invoice is approved.

How are quarterly and annual rebates managed?

ininvoice does not calculate rebates or track tiers. When the rebate credit note arrives, it is linked to the invoice it cites, by invoice number and supplier tax ID. Checking the amount against the agreed tier table is procurement’s job, and a person approves the credit note before it is exported.

Do I need a formal PO for every order to every supplier?

For line-by-line matching, yes: ininvoice compares the invoice against the purchase order (with the agreed price) and the delivery note. Purchase orders and delivery notes come in like invoices, by e-mail or upload. Without a PO there is no agreed price to compare each line against.

How does the system separate per-line discounts from header discounts?

Line by line, reading each discount applied on the invoice. The net unit price per line is what is compared to the PO price. Header totals are never compared.

What integrations does it have with distribution ERPs?

ininvoice exports clean data as a CSV or Excel file importable into your ERP. Holded and Sage 50/200 are the most common in the Spanish distribution SME ICP. Distrito K, Solmicro and other vertical ERPs take the same file through their own import; there is no native connector.

How long does it take to be operational at a distributor?

It starts when you connect the inbox: without implementation or a consultant, it is up and running in 24–48 hours. Extending to the rest of suppliers and branches depends on volume.

Does it replace the ERP or accounting?

No. ininvoice is pure AP automation. It is not ERP, accounting or stock management. It sits between the supplier inbox and your ERP. Approved invoices are exported as a CSV or Excel file that Holded, Sage 50/200, Distrito K or equivalents can import.

Three things to remember

Wholesale distribution is not just another AP case. With 2-5% gross margins and thousands of active SKUs, it is one of the sectors where manual AP eats most margin silently — and where there is most room for good automation.

1. Manual AP at distributors with 100-300 suppliers eats between 1% and 3% of purchases in undetected errors. On EUR 5M/year that is EUR 50,000-150,000 of lost margin per year.
2. Generic touchless will not do. You need to match line by line against the PO price, manage partial deliveries, link rebate credit notes to their invoices and make sure each exception reaches whoever decides.
3. The stack that works is light: supplier inbox → AP automation layer → ERP. The BI feeds the margin dashboard in parallel. No big projects, no six-month consultancy.

If you want to see how your flow looks with one real branch, try ininvoice with your own invoices. Pricing is tailored: a proposal within 48 hours of seeing your invoices.

Related content

• Three-way matching: cross-checking invoice, PO and delivery note line by line
• Touchless accounts payable: what it means and how to measure it
• Managing invoices in distributors: base guide by supplier
• IDP vs classic OCR: why OCR is not enough for distribution