Skip to main content Standardize Payable request → Invoice capture → Approval → Payment → Journal in Sanka. Anchor on Bill and Purchase Order, layer AI capture, and enforce approvals to prevent missed or duplicate payments.
Use cases
Payables control : Centralize payment requests, due dates, and cash-out visibility.AI at https://invox.jp/ - demo : Capture supplier invoices with AI to auto-extract items, tax, and due dates.Payable Ops : Three-way match Bill and Purchase Order so only received items are payable.
Sanka setup essentials
Use Company for vendors, Purchase Order for buying, Bill for invoices, and Payment (with payment type) for disbursements.
Map AI capture fields to Bill properties (invoice number, due date, bank info, tax).
Configure Workflow rules for amount-based approvals and define an exception path for urgent payments.
Operating steps
Intake : Buyers submit payables tied to a Purchase Order; require approval for non-PO submissions.AI capture : Ingest PDFs via inbox/forwarding; AI draft-fills Bill.Match & validate : Three-way match quantities/amounts; escalate deviations for review.Approve : Route by amount/department/project; log approvals on the Bill.Pay & post : Record Payment with method/date; export or sync journals to accounting.
Automation ideas
Workflow actions : Remind owners 3 days before due if the Bill is still pending approval.Object actions : Keep drafts flagged if AI capture is incomplete; block routing until required fields are filled.Record actions : Alert buyers when PO vs. Bill variance exceeds tolerance.
Reporting and oversight
Weekly/monthly cash-out forecasts from the payables calendar.
Dashboards for duplicate/late payments by vendor.
PO-to-Bill variance tracking to improve purchasing accuracy.
