Overview
When Junipeer syncs orders from your e-commerce platform to your ERP, the data does not just create orders — it feeds into your accounting. Invoices are generated, payments are recorded, VAT is calculated, and revenue is posted to the correct accounts. Getting these accounting settings right is essential for accurate bookkeeping.
This guide covers the key accounting concepts that apply to most Junipeer integrations, regardless of which specific platforms you use.
Sales accounts
A sales account (or revenue account) is the bookkeeping account where revenue from each sale is recorded. In most ERP systems, you need at least one sales account, but many businesses use several — typically one per VAT rate.
For example, a business selling domestically might have:
A sales account for standard-rate VAT (e.g., 25%)
A sales account for reduced-rate VAT (e.g., 12% or 6%)
A sales account for zero-rated or exempt sales
How this is configured in Junipeer depends on your ERP. Some systems require explicit sales account mapping per VAT rate in Configure > Settings, while others use customer classes, tax groups, or built-in tax engines that handle account assignment automatically. Refer to the connector-specific guide for your ERP to see what is required.
VAT handling
Junipeer reads the VAT information from each order line item in the e-commerce platform and passes it to the ERP. How the ERP processes that VAT data varies — some systems require you to map each VAT rate to an account in Junipeer's settings, while others resolve the correct account automatically based on their own tax configuration.
Things to verify before going live:
All VAT rates used in your e-commerce platform exist or are recognized in your ERP
Any required mappings in Junipeer's settings are configured (check the connector-specific guide for your ERP)
If you sell physical goods and digital goods at different VAT rates, both rates are covered
If a VAT rate on an incoming order cannot be resolved in the ERP, the sync will typically fail for that order. Check Logs for the specific error and add the missing configuration.
OSS VAT (EU cross-border sales)
If you sell to consumers in other EU countries, the One Stop Shop (OSS) regulation may apply. Under OSS, you charge the VAT rate of the buyer's country rather than your own country's rate. This means a single order can contain line items taxed at, say, 21% (Netherlands), 19% (Germany), or 22% (Italy).
How Junipeer handles OSS depends on your ERP:
Some ERPs require explicit mapping — you configure each country's VAT rate to a specific sales account in Junipeer's settings. For businesses selling across many EU countries, this can mean dozens of mappings. Some systems support CSV import for bulk configuration.
Some ERPs use customer classes or tax groups — the ERP resolves the correct account automatically based on the customer's country and its own tax rules. In this case, little or no additional mapping is needed in Junipeer.
Some ERPs handle it fully automatically — the system has a built-in OSS/tax engine and requires no extra configuration beyond enabling the feature.
Check the connector-specific guide for your ERP to see which approach applies.
If you are unsure whether OSS applies to your business, consult your accountant. Junipeer handles the technical mapping, but the decision of which tax rules to apply is a business and legal matter.
Payment methods and terms
When an order is synced to your ERP, Junipeer needs to know how to record the payment information. This is configured in Configure > Settings > Payment Methods.
Payment method mapping tells Junipeer which ERP payment method corresponds to each payment type in the e-commerce platform. For example, a payment made through a buy-now-pay-later provider in the webshop might map to a specific accounts receivable account in the ERP.
Payment terms define when payment is expected. For e-commerce orders that are already paid at checkout, the payment term is typically "0 days" (immediate). The default payment term is set in the Payment Methods settings and applied to all synced orders unless overridden.
Each payment provider used in your webshop should have a corresponding payment method configured in both the ERP and in Junipeer's mapping. Missing mappings will cause order sync failures.
Payment reconciliation
Payment reconciliation is the process of matching what customers paid (via your payment provider) with the invoices in your ERP. Without automation, this is a time-consuming manual task — especially for high-volume stores that process hundreds or thousands of orders per day.
Junipeer automates this through the payout flow (see Order Sync for the full lifecycle). The key steps are:
Invoices get unique reference numbers — when Junipeer creates invoices in the ERP, each one carries a reference that links it back to the original e-commerce order and payment transaction.
Payout reports are received — your payment provider sends settlement reports (via webhook or scheduled fetch) detailing which transactions are included in each bank deposit.
Transactions are matched to invoices — Junipeer uses the reference numbers to match each transaction in the payout report to the corresponding invoice in the ERP.
Invoices are marked as paid — matched invoices are updated with the payment date and amount.
Fees are written off — payment provider fees (processing fees, transaction costs) are booked to a separate fee account, keeping your revenue accounts accurate.
The fee account is configured in your payment method settings. Make sure this account exists in your ERP before enabling payout reconciliation.
Shipping costs
Shipping costs from e-commerce orders are synced as part of the order data. How they appear in the ERP depends on your settings:
Shipping can be posted to a dedicated shipping revenue account
The shipping method mapping in Configure > Settings > Shipping Methods controls how the e-commerce platform's shipping methods translate to the ERP
If shipping is free (zero-cost), the line is still synced but with a zero amount. If shipping methods are not mapped, the sync may fail or use a default value — check your settings to be sure.
Currency handling
Junipeer passes the order currency from the e-commerce platform to the ERP. For this to work:
The order's currency must be enabled in the ERP
If your ERP requires exchange rates, those rates need to be current
Multi-currency orders (where the customer pays in a different currency than your base accounting currency) are handled by the ERP's built-in currency conversion. Junipeer ensures the correct currency code is passed with each order.
If you sell in multiple currencies, verify that all currencies are enabled in your ERP before starting to sync. A missing currency will cause order sync failures.
Tips
Work with your accountant when setting up VAT and revenue account configuration. These settings directly affect your financial reporting.
Test with a few orders in different scenarios (domestic sale, EU cross-border, different payment methods) before going live to confirm all mappings are correct.
If you add a new payment provider to your webshop, remember to add the corresponding payment method mapping in both your ERP and in Junipeer's settings.
Review your fee account periodically to ensure payment provider fees are being tracked correctly.
For stores with high order volumes, enabling payout reconciliation can save hours of manual bookkeeping per week.