Use Claude or Codex to draft bills and expenses, check policies, route approvals, prepare payouts, and review audit logs in Sanka.
Last updated: May 17, 2026
This guide shows how to use Claude or Codex connected to Sanka to move spend through draft -> review -> approval -> payout prep -> accounting review. Start by asking AI to read supplier invoices, receipts, or card statements and prepare drafts, then confirm the details before anything is approved or marked as paid.
Claude/Codex
vendor-invoice.pdftaxi-receipt.jpg
Please prepare spend drafts from these files. Check the vendor, requester, amount, tax, due date, approver, duplicate candidates, and missing information. Do not approve or mark anything as paid yet.
Preparing spend drafts in SankaI prepared spend drafts from the attached files. Please review the vendor, amount, tax category, requester, department, approver, payment timing, and missing information before approval.
Ask for another check...
Before you start
Check that you have the following ready.
Claude or Codex is connected to Sanka
Vendors, employees, departments, projects, and approval rules are available in Sanka
Supplier invoices, receipts, or card statement files are ready to attach
Your team has spend categories, tax treatment, payment methods, and payout schedules defined
You have permission to create spend records, review approvals, and prepare payments
Open a new chat in Claude or Codex, attach invoices or receipts, and ask it to prepare spend drafts. Keep the first step as a draft so finance can review it before approval or payment.
Sample prompt
/sanka I attached supplier invoices and receipt files. Please create spend drafts and show the vendor, amount, date, due date, tax treatment, requester, department, approver, duplicate candidates, and missing information. Do not approve or mark them as paid yet.
Ask the AI to check:
Invoice or receipt date, amount, currency, due date, and tax treatment
Vendor, employee, business purpose, and spend category
Department, project, cost center, and payment method
Duplicate candidates with the same date, amount, vendor, or receipt
Unreadable or missing evidence
Amounts, vendors, or categories that change the approval route
Review before approval
After the draft is prepared, review the spend record in Sanka. Ask the AI to explain what it read from the document and which fields need human confirmation.
Sample prompt
/sanka Review this spend draft before approval. Check whether the document matches the entered amount and due date, whether a similar record already exists, and whether the selected approver is correct. Do not approve it yet.
If anything needs attention, update the draft before approval. If the document is unclear or the spend may violate policy, ask for a clearer file or additional explanation.
Check the approval route
Once the draft is correct, route it for approval. Approval routing can use amount, category, department, vendor, project, or company policy.
Sample prompt
/sanka Show the approval route for this spend draft before I submit it. Explain who will approve it, why that route applies, and whether any document, due date, or policy issue blocks submission.
Common approval patterns include:
Small office expenses go to the direct manager
Larger supplier bills require finance or department head review
Requests without evidence stay pending until the file is attached
Project-related spend also routes to the project owner
Prepare payout and accounting
After approval, prepare payout or payment records according to your team's rules. Before marking anything as paid, review bank transfer, reimbursement, company card, or supplier payment handling.
Sample prompt
/sanka This approved spend is ready for payout preparation. Prepare a payment draft and show the payee, amount, payment method, scheduled payment date, linked spend record, and accounting review fields. Do not mark it as paid yet.
Before confirming payment, check:
The approved amount and payment amount match
The payment method and scheduled payment date are correct
The spend record and payment draft are linked
Supplier payment, employee reimbursement, and company card handling are not mixed
The status changes to paid only after payment is complete
Checkpoints
Use Sanka logs and tables to review AI-prepared drafts, approvals, payout prep, and accounting review. Logs help finance teams see who changed what and when.
