POS and Fortnox: from daily close to reconciliation

Once service is over, the restaurant’s sales need to reach its bookkeeping system. Connecting your POS to Fortnox can remove the need to enter the same figures again. The useful result is a clear process showing what arrived and what still needs attention.

Define what the connection should transfer

Start with the transactions your restaurant handles: dine-in service, takeaway, cards, Swish, cash, invoices and any gift cards. Ask the supplier to demonstrate how it handles sales groups, VAT categories, payment methods, discounts and refunds.

Check whether the integration creates posted accounting entries, records awaiting approval or something else. Establish when transfers happen and how you confirm success. Offering a Fortnox connection does not mean every supplier transfers every record in the same way.

Connect the company and configure accounts

Fortnox describes an activation process where you log in to the correct Fortnox company and approve the integration’s permissions. Follow Fortnox’s current connection guide, in Swedish, and the supplier’s instructions.

Then review the chart of accounts with whoever handles your bookkeeping. Agree on accounts, VAT codes and any cost centres. A sales group called “drinks” may contain products with different VAT rates; its name alone cannot determine the accounting treatment.

Gift cards, tips and advance payments also need handling that reflects how they work in your business. Review the configuration when products, payment flows or VAT rules change.

Sales and bank deposits are different figures

Consider a simplified example: guests pay a total of SEK 11,200 by card. The payment provider deducts SEK 100 in fees and pays out SEK 11,100. The deduction does not reduce the original sales by SEK 100.

The POS report shows sales and their VAT. The settlement statement explains which payments, fees and adjustments make up the payout. The bank account shows the money received. Timing differences between the sales date and payout date also need explaining.

Transferring a Z-report therefore does not complete bank reconciliation. Decide who compares the records and investigates differences.

Test the transactions that cause questions

Run a controlled test with the supplier and your bookkeeper. Follow an ordinary sale, a refund and a payment split across payment methods through the complete process. Include gift cards or invoicing if your restaurant uses them.

Check that:

• amounts, VAT, dates and references match
• retrying a transfer does not post the same daily close twice
• failed transfers are visible and can be followed up
• corrections retain a clear connection to the original records.

Vendion requires an internet connection. Agree on a procedure for connection or transfer failures, including how to confirm that no records are missing afterwards.

Measure your own workload

Measure time spent entering, checking and correcting records before and after implementation. In an illustrative calculation, reducing this work from 15 to 5 minutes over 26 working days saves 260 minutes: 4 hours and 20 minutes. This is an example, not a promised saving.

Compare that value with the integration licence, Fortnox subscription, setup and any bookkeeping support. Automation can reduce repeated entry, but incorrect configuration can also repeat the same mistake.

Fortnox and Vendion

Vendion Integration provides the direct Fortnox connection. Distinguish that licence from file-based payroll data export in Vendion Staff. Payroll records, sales bookkeeping and bank reconciliation are separate workflows. Check current pricing and review the Fortnox licences and settings your restaurant requires.

The Swedish Accounting Standards Board explains that responsibility for bookkeeping remains when you get help. A useful integration reduces data entry and provides better records for those checks.

See Vendion live and follow a daily close from the POS into bookkeeping.