Prerequisites
Confirm the following before APIWorx provisions the connector. Each item maps to a configuration step that cannot be completed without it, so a gap here stops setup partway through rather than at first sync.- Admin access to your Weel organization, used to authorize the Weel API connection.
- Admin access to your DualEntry company, used to authorize the DualEntry connection and confirm account mappings.
- Your chart of accounts finalized in DualEntry. Each Weel category or budget is mapped to a GL account, so the target accounts must exist before mapping.
- Your GST tax treatments configured in DualEntry, so the connector can carry the GST amount and rate from each Weel transaction to a matching DualEntry tax line.
- Departments or projects set up in DualEntry if you plan to map Weel teams to a dimension. This mapping is optional.
- An APIWorx engagement for the DualEntry + Weel connector. APIWorx hosts and operates the connector; the setup steps below are completed with your APIWorx implementation contact.
How the connector works
The connector moves card spend from Weel into DualEntry in a single direction through APIWorx. A new or settled card transaction, or an approved expense in Weel, triggers the sync; APIWorx retrieves the record, applies your mappings, and posts the result to DualEntry. Webhooks drive near real time syncs where Weel exposes them, and a configurable batch schedule covers everything else. APIWorx runs the connector as a managed service on its own infrastructure, with continuous monitoring and logging. You do not host or run anything yourself, and there is no Weel connector tile inside the DualEntry application. Mapping changes and sync settings are maintained through APIWorx rather than in DualEntry. The connector performs six jobs on each synced record:- Spend capture. Retrieves Weel card transactions and reimbursements, including merchant, amount, currency, date, cardholder, budget or team, category, and GST.
- GL coding. Maps each Weel category or budget to a DualEntry GL account and applies department or project dimensions where configured.
- Tax handling. Carries the GST amount and rate to the matching DualEntry tax treatment.
- Posting. Creates the corresponding expense or card-payable entry in DualEntry, attributed to the cardholder and budget.
- Reconciliation. Matches each posted transaction to the Weel card statement and settlement so the card-payable balance in DualEntry reconciles to Weel.
- Updates and reversals. Reflects edits, recategorizations, and refunds made in Weel as adjustments in DualEntry.
What syncs into DualEntry
The connector imports two record types from Weel: card transactions and reimbursable expenses. Both arrive in DualEntry as posted entries attributed to the cardholder and the Weel budget that incurred the spend, so the resulting records carry through to your AP and GL workflows the same way a manually entered card expense would. The table below summarizes what flows from Weel into DualEntry on each sync:
Edits made in Weel after a record has synced (recategorizations, amount changes, refunds) come through as adjustments rather than duplicate postings, so the DualEntry balance tracks the current state of the Weel transaction.
Field mapping
The connector maps each Weel transaction field to a DualEntry field during posting. The mapping below is representative; your APIWorx configuration sets the exact category-to-account and team-to-dimension rules for your chart of accounts.
The category-to-account and team-to-dimension rows are the two mappings you maintain over time. When you add a GL account or restructure budgets in Weel, update the corresponding mapping in APIWorx so new categories continue to post to the correct account rather than the default holding account.
Configure the connection
Set up the connector with your APIWorx implementation contact. APIWorx authorizes both systems and records the mappings the connector applies on every sync. Work through the items below in order; the mappings depend on the connections being authorized first.- Authorize the Weel API connection. Connect APIWorx to your Weel organization at the organization level so the connector can read card transactions and expenses.
- Authorize the DualEntry company connection. Connect APIWorx to the DualEntry company that receives the postings.
- Map categories and budgets to GL accounts. For each Weel category or budget, choose the DualEntry GL account it posts to. Unmapped categories route to a default holding account and are flagged, so map every category you expect to see.
- Map teams to dimensions (optional). If you track spend by department or project, map each Weel team to the corresponding DualEntry dimension.
- Configure GST and currency handling. Map Weel GST to the matching DualEntry tax treatment and confirm how foreign-currency transactions are handled.
- Choose the sync mode. Select live event syncing (webhook-driven, near real time) or a scheduled batch, depending on how quickly you need spend to appear in DualEntry.
Handle GST and tax
The connector carries GST from each Weel transaction to a DualEntry tax line, which matters because Weel is an Australian platform and most transactions include GST. During configuration you map Weel’s GST to a DualEntry tax treatment; on each sync, the connector reads the GST amount and rate on the Weel transaction and posts a matching tax line in DualEntry rather than rolling tax into the expense amount. Because tax is posted as a separate line, the GL account mapped to the category receives the net expense and the GST treatment receives the tax. If a transaction’s GST does not match what the mapped treatment expects, the connector raises a tax mismatch exception (see Monitor sync health and exceptions) rather than posting a figure that would not reconcile against the Weel statement. For how tax treatments are defined in DualEntry, see Non-US taxes.Monitor sync health and exceptions
The connector surfaces every exception through the APIWorx portal and does not fail silently, so the portal is where you confirm that spend is flowing and find records that need attention. Each sync writes a log entry recording the source transaction ID, the action taken, and the result; APIWorx retains these logs for troubleshooting and audit. The connector raises three kinds of exception:Transient failures retry automatically, so a record in the error list is not necessarily lost. Check whether the connector has already retried and cleared it before reprocessing manually.