Less invoice entry
Create accounts payable invoices directly in Restaurant365 from the records in opsi.
Restaurant365 + opsi
Export processed invoices from opsi to Restaurant365 with vendor, location, and GL account details, so your accounting team can skip re-entry.
Direct invoice exports · Mapped to your Restaurant365 accounts
1
→ opsiPrepared operational data
2
→ Restaurant365Accounting destination
3
Ready for accountingMappings and requirements below
Opsi handles invoice processing and review. When you export, Restaurant365 receives the accounting record with your vendor and expense categories already mapped.
Why operators turn this on
Keep the invoice work in opsi and the books in Restaurant365. Send each prepared invoice to accounts payable with its number, dates, amount, and location.
Your expense categories
Group invoice amounts by GL account, with configurable accounts for tax, shipping, and other charges.
Credits and paid purchases
Export vendor credits as credit memos and purchases with a mapped funding source as journal entries.
A source to check
Invoice notes carry export details and a link to the original document when available.
What moves between the two
| Data | Direction | Notes |
|---|---|---|
| Vendor invoices | opsi → Restaurant365 | Accounts payable invoices with invoice number, dates, vendor, location, and amounts grouped by GL account. |
| Vendor credits | opsi → Restaurant365 | Credit memos with the mapped vendor, location, and expense accounts. |
| Paid purchases | opsi → Restaurant365 | Journal entries when a funding source is mapped, allocating expenses against the payment account. |
| Source document link | opsi → Restaurant365 | The original invoice URL is included in export notes when available. |
| Accounting reference data | Restaurant365 → opsi | Vendors, GL accounts, funding accounts, and locations for setup and mapping. |
Invoice amounts are grouped by mapped GL account. Vendors, accounts, and locations are read from Restaurant365 to support the export.
Who it’s for
Accounts payable teams
Receive prepared invoices in Restaurant365 without entering the same bill again.
Accountants & bookkeepers
Keep invoice expenses aligned with the chart of accounts you already use.
Managers & owners
Keep invoice handling and the accounting handoff in one workflow.
Restaurant groups
Link each opsi location to the appropriate Restaurant365 location.
Questions we get
What can I export to Restaurant365?
Vendor invoices become accounts payable invoices, vendor credits become credit memos, and purchases with a mapped funding source become journal entries. Amounts are grouped by GL account.
When are invoices sent?
Exports are on demand. Choose the invoices to send from opsi after processing and review.
Does the source invoice go with the export?
When a source document is available, its URL is included in the export notes. Restaurant365 receives a link to that document.
What do I need to connect?
You’ll need your Restaurant365 instance name and API token, a location to connect, and vendor and GL account mappings. Map funding sources as well if you export paid purchases.
Connect the workflow
Ready to connect Restaurant365?
Give your accounting team prepared invoices without another round of data entry.