From purchase order to paid — one governed ledger, no re-keying
A complete purchase-to-pay loop — vendors, POs, goods receipt, three-way matching, bills, and batch payments, all posting to the GL.
Everything Procurement (P2P) handles
Vendors with payment controls
Vendors carry payment terms, early-pay discounts, masked bank detail, and hard blocks for payment or purchasing — and can’t be deleted while open POs, unpaid invoices, or pending payments exist.
Purchase orders with an enforced lifecycle
POs move through a validated state machine — draft, pending approval, approved, received, closed — where illegal transitions raise rather than silently corrupt state.
Multi-level approval with segregation of duties
Per-company amount-threshold approval levels, by role or specific user, enforced sequentially with row-locking and a full audit log — auto-approving only when no matrix is configured.
Real three-way matching
Each invoice line is matched against the PO and goods receipts for price and quantity within tolerance; out-of-tolerance invoices get a payment block until they’re cleared.
AI-assisted bill capture with review
Drop a vendor document into the OCR inbox — Sebee extracts it, auto-matches the vendor, runs duplicate and sister-company checks, and a person confirms before anything posts.
Batch payment runs with FX
Run a cash-position check, generate proposals, submit, approve, and create payments — translating foreign bills to base currency and recognizing realized FX gain or loss on settlement.
From action to ledger, in four steps
- 1Raise & approve
Create a purchase order; if it crosses a threshold it routes through the approval matrix with a full audit trail.
- 2Receive
Record receipt against the PO — posting inventory against GR-IR clearing and allocating any landed cost.
- 3Capture
Drop the vendor’s bill in the OCR inbox or key it in; three-way matching validates it against the PO and receipt.
- 4Pay
Approve the bill and run a single or batch payment — clearing GR-IR and AP and recognizing discounts, PH withholding, and realized FX.
Real screens, real data
Built for Philippine withholding
Vendors carry BIR expanded-withholding-tax settings, and the bill poster books EWT-payable and keeps the withholding amount consistent with BIR EWT reporting — so compliance is baked into the posting, not bolted on after.
What you get
- One governed flow from PO to payment — no re-keying between procurement, AP, and the GL.
- Spend is controlled up front: threshold approvals and payment blocks stop unapproved bills.
- Foreign-currency purchases post correctly, with realized FX recognized on payment.
- Segregation of duties on approvals — whoever creates a payment can’t approve it.
- Faster bill entry with Sebee’s capture, and a person always confirms before it hits the ledger.
Frequently asked questions
Does LedgerQ do three-way matching?
Yes. Each invoice line is matched against the PO and goods receipts for price and quantity within tolerance; out-of-tolerance invoices get a payment block until they’re cleared.
Can I capture vendor bills automatically?
Drop a vendor document into the OCR inbox — Sebee extracts it, auto-matches the vendor, and runs duplicate and sister-company checks — and a person confirms before anything posts.
How is Philippine withholding handled?
Vendors carry BIR expanded-withholding-tax settings, and the bill poster books EWT-payable and keeps the withholding amount consistent with BIR EWT reporting — so compliance is baked into the posting.
How do foreign-currency payments post?
Batch payment runs translate foreign bills to base currency and recognize realized FX gain or loss on settlement. Segregation of duties applies — whoever creates a payment can’t approve it.