Lesson 3 of 5 · 8 min read
How AION automates Procure-to-Pay
Every step of the P2P cycle in AION, with the specific features that automate it. The SLA engine posts journal entries automatically — your accountant never touches the GL for routine transactions.
Where each step lives in AION
| Step | AION menu | What it does for you |
|---|---|---|
| 1. Requisition | Procurement → Requisitions | Auto-generate from low-stock alerts or create manually |
| 2. Req approval | Approvals → Pending | Multi-level approval chain based on amount + cost center |
| 3. Purchase Order | Procurement → POs | One-click conversion from approved requisition |
| 4. PO approval | Approvals → Pending | Second-level sign-off with email + in-app notifications |
| 5. Goods receipt | Inventory → Receiving | Scan/key in lot numbers, expiry, serial numbers |
| 6. Invoice receipt | AP → Invoices → New | OCR upload or manual entry with supplier auto-complete |
| 7. 3-way match | AP Invoice → Match button | System validates PO/Receipt/Invoice in one click, flags exceptions |
| 8. Invoice approval | Approvals → Invoices | Approve queue with attached PO + receipt for context |
| 9. Payment | AP → Payments | Bulk payment runs, wire transfers, partial payments |
| 10. Bank rec | Cash Mgmt → Bank Rec | Import bank CSV, auto-match to payments |
The SLA engine — how journal entries post themselves
Most ERP systems require an accountant to manually post journal entries. AION has a dedicated module called SLA (Subledger Accounting) whose entire job is converting business events into balanced journal entries automatically.
The flow:
- You perform a business action — approve an invoice, receive goods, record a payment
- The subledger emits an event (e.g.,
INVOICE_APPROVED) - The relevant SLA resolver (one for payables, one for receivables, one for inventory, etc.) determines the correct DR/CR accounts based on your chart of accounts configuration
- A balanced journal entry is created and posted to the GL
- Your trial balance updates in real time
You never click “Post to GL.” You never open the JE form. The entries just appear.
For P2P specifically, two SLA resolvers are involved:
- Inventory SLA resolver — triggers on receipts, posts the Raw Material / AP Accrual entries
- Payables SLA resolver — triggers on invoice approvals and payments, posts the AP / Bank / VAT entries
AION-specific features that fix the six SMB problems
A. Automated three-way match
When you approve an AP invoice, AION looks up the linked PO and receipt automatically. It compares:
- Item + quantity (with tolerance)
- Unit price (with tolerance)
- Total amount
If any line fails tolerance, the invoice is blocked with a clear exception message. You can override with a documented reason — creating an audit trail.
No Excel. No stack of papers. 5-15 hours a month back to your accountant.
B. Automatic accrual at receipt
When warehouse marks goods received, AION posts DR Raw Material Inventory, CR AP Accrual immediately. No wait for the invoice. No month-end correction. Your liability is always accurate.
When the invoice eventually arrives and gets approved, the accrual is cleared and the real AP balance is posted. This is called a GRIR (Goods Received / Invoice Received) reconciliation and AION runs it continuously, not at month-end.
C. Duplicate invoice prevention
Supplier + invoice number is a unique key. If you try to enter the same invoice twice, AION blocks it before it’s saved. Simple, but it eliminates 0.5-1% of spend leakage.
D. Full audit trail on everything
Every action in the P2P cycle is logged:
- Who created the requisition
- Who approved it (with timestamp)
- Who converted it to PO
- Who approved the PO
- Who received the goods and when
- Who entered the invoice
- Who approved it
- Who recorded the payment
All searchable. All exportable. Auditor asks “who approved PO-2026-00456?” — you click, they see.
E. Costing that matches reality
When you receive goods, the unit cost is captured at that exact moment — including any exchange rate variance if the PO was in a foreign currency. AION uses period average costing, which rolls up all receipts in the period and calculates a weighted average per item, per warehouse.
When inventory issues to production, the costing engine uses the correct period average. Your COGS is as accurate as your receipts.
F. Commitment visibility
Every approved PO shows up on the Open POs and Commitment reports. “How much are we committed to pay next 30 days?” is a single report, always current.
Configuration you do once
To make all this work, you configure (during implementation):
- Chart of accounts — which accounts represent Raw Material Inventory, AP Accrual, Accounts Payable (by supplier), VAT Input, Bank, etc.
- SLA account rules — which accounts to post to for which event types
- Approval workflows — amount thresholds, approver roles, delegation rules
- Three-way match tolerances — how many SAR / what % difference triggers an exception
- Supplier master — payment terms, tax treatment, bank details
After that, P2P runs itself.
Next lesson
In Lesson 4 — Lab, you’ll walk through this flow end-to-end in our live demo. You’ll log into the Oasis Fresh (Saudi) BG and buy 500L of mango concentrate from Cairo Citrus Co. — watching every GL entry post automatically. The same flow runs in Pearl F&B (Qatar) and Nile Foods (Egypt).