The Autopay Connector imports invoices from Autopay into Business Central. Each imported invoice
carries its items — parking sessions, charging sessions and fees — and its payments. From
that data the connector creates or updates customers, creates sales invoices and lines, and
posts paid invoices through journals, all according to the rules on the setup page.
| Concept |
Meaning |
| Imported invoice |
An Autopay invoice pulled into the Invoice List, with header, client details, items and payments. |
| Invoice item |
A line on an imported invoice: a parking session, a charging session or a fee, with price, VAT and session details such as facility, zone, vehicle and entry and exit events. |
| Invoice payment |
A payment received against an imported invoice, with channel, provider, amount and transaction references. |
| Client |
The Autopay party behind an invoice. Its client ID maps to a Business Central customer. |
| Client type |
Regular, Tenant, Landlord or Company. Processing, fees and merging are switched on per type. |
| Paid and unpaid invoices |
Paid invoices are processed into journals or sales documents; unpaid invoices become sales invoices, optionally merged and with an invoice fee. |
| Processing ID |
The identifier written on everything the connector creates from an invoice, linking sales documents, journal lines and ledger entries back to the Invoice List. |
| Payment channel |
An Autopay payment channel mapped to a balancing account, payment method, and the G/L accounts and VAT groups for parking and charging sessions. |
| Sales line values |
The item or G/L account, description and VAT posting groups used when a sales line is created for an invoice item type at each VAT rate. |
| Skipped |
A flag on an invoice, item or payment that excludes it from processing. |
- Import. The connector retrieves invoices from Autopay for the import window on the setup
page, on demand with Perform Import or for a chosen range with Import Data (Custom).
Imported invoices appear in the Invoice List.
- Customers. Client data creates or updates customers, using the domestic and international
customer templates, the option to use the client company number as customer number, and the
default customer for clients without an ID.
- Processing. Process Invoices turns eligible invoices into sales invoices and lines,
using the sales line values and dimensions from setup. Unpaid invoices for tenants and
companies can be merged. Paid invoices are processed via journal, using the payment channel
mappings.
- Posting. Sales headers can be released on creation and posted automatically by a job
queue, a configured number at a time.
- Traceability. The processing ID and invoice ID follow the data onto sales documents,
journal lines and ledger entries, and Show Related Data opens what was created from any
invoice or payment.
| Standard page |
What is added |
| Sales Invoice |
Actions to show the Autopay invoice items and payments behind the document; a read-only long description on lines. |
| Posted Sales Invoice |
The same actions, plus Show Sent E-Mail. |
| Posted Sales Invoices |
Send Invoice Detail, which emails the details of merged invoices. |
| Customer Card |
Invoice Detail E-Mail, Autopay ID, skip flags, Parent Customer No., Date of Birth and fee flags. |
| Cash Receipt Journal, Customer Ledger Entries, General Ledger Entries, G/L Entries part |
Processing ID and Invoice ID, normally hidden. |
| Role |
Works mainly with |
| Finance and operations staff |
Invoice List, Invoice Items, Invoice Payments, sales documents |
| Administrator |
Setup, Payment Channels, Sales Line Values, Descriptions, automatic posting |
- Microsoft Dynamics 365 Business Central.
- Autopay API credentials (client ID and client secret) provided by Autopay.
- Install the extension.
- Work through the quick start in a sandbox
company.
- Complete the setup.