<media type="image" src="…"/>
as a child of <hero>, switching this page to the
full-bleed dark variant.
Recommended : 1920 × 1080 px (16:9)
Formats : PNG · JPEG · WebP · SVG
Off-spec uploads are rejected — aspect ratio outside 16:9 ±2 %, dimensions outside 800 × 450 … 3840 × 2160.
Supplier invoices matched, approved and paid against the operational truth.
A payables surface that reconciles every invoice against its purchase order and goods receipt before the payment proposal goes near the bank — with withholding tax, retentions and the local fiscal regime applied at the engine level.
Three-way match
Purchase order, goods receipt, supplier invoice — reconciled by the engine before approval. Discrepancies routed to the right operational owner, not held in an invoice queue.
Supplier master
Multi-entity supplier records with bank details, payment terms, currency, tax treatment, withholding profiles and document-management linkage.
Payment proposal
Due-date-driven proposal generation with cash position awareness, discount-take optimisation, supplier-priority overrides and approval workflow up to the CFO.
Automated payment-file generation
SEPA credit transfers, Norma 34, confirming, factoring instructions — generated from the proposal, signed and delivered through the bank's preferred channel.
What the AP surface covers
Supplier master and onboarding
Multi-entity supplier records, KYC documentation, certificate of standing, bank-account proof, sanctions screening, periodic re-verification.
Three-way match engine
Quantity, price, currency and tax tolerances configurable by category. Within-tolerance auto-match; out-of-tolerance routed to the buyer or the receiver, not held in finance.
Approval workflow
Multi-level approval by amount, category, supplier or cost centre. Out-of-office delegation, full traceability of who approved what and when, and segregation-of-duties controls.
Withholding and retentions
IRPF in Spain, retenciones in LATAM regimes, withholding tax on international payments — applied at the line level, reported on the period's fiscal output.
Cash forecast contribution
Approved payables feed the cash-forecast surface. The treasury team sees the next 30, 60 and 90 days of committed outflows updated as invoices approve.
Document management
Supplier invoices, supporting documentation, signed approvals and remittance advices stored against the invoice, retrievable from the audit screen, retention-policy aware.
Why three-way match is the engine, not the policy
Most enterprises have a three-way match policy. The policy lives in a procedures document and is enforced — variably — by a payables clerk reading invoices against a paper PO and a goods-receipt note. The result is a queue of unresolved invoices, ageing past their due date because the operational owner who could resolve the discrepancy is not in the loop.
Axional treats three-way match as an engine behaviour. The PO, the goods receipt and the invoice are three rows in the same database, joined by the same key. The match happens automatically; the unmatchable cases route to the operational owner with the discrepancy named. Finance sees the queue shrink, not grow, as the operation runs.