Automate e-conomic work with your agents

Trigger: Your bookkeeper wants to know whether every order the shop shipped last month was invoiced in e-conomic.

With Maplith:

1. Route: route from the shop order to the booked invoice in e-conomic by the order reference, and says how much Maplith trusts that hop.
2. The map: get_object on the booked invoices says the order reference sits in the field e-conomic calls other reference, with the rate a scan measured for that join. The agent lists last month’s orders in your shop with its own access.
3. Findings: Where the last scan of the exports saw orders with no invoice against them, a finding names the gap, with its evidence and a recommendation.
4. The action gate: request_action for a task for the bookkeeper with last month’s order references and the field to match them on in e-conomic, decided by the key’s policy. The bookkeeper checks and books them in e-conomic.
5. Record and value: record_action records that the list reached the bookkeeper, and how the month closed.

Result: The bookkeeper checks last month’s orders against e-conomic by the reference it books them under.

Trigger: Before chasing an invoice, sales asks which customer in e-conomic a company in the CRM is.

With Maplith:

1. Ask: ask: “how do e-conomic’s customers tie to companies in the CRM?” The answer cites the joins it rests on: the CVR number of a business customer first; a match by name is weaker.
2. Route: route from the CRM company to the e-conomic customer by CVR number, then on to its booked invoices by customer number.
3. The map: get_object on the CRM company says which field holds its CVR number; the agent reads that field in the CRM with its own access.
4. The action gate: request_action for a task for the bookkeeper: the CRM company, its CVR number, and the route to its booked invoices to look up in e-conomic.
5. Record and value: record_action records who got the task and what they found.

Result: The bookkeeper finds the company in e-conomic by the number both systems share, not by a name that may differ.

Trigger: A payout from your payment provider is in the bank, and the entries in e-conomic for that day do not seem to add up to it.

With Maplith:

1. Route: route from the payout to e-conomic’s entries by date and amount, and from the entries to the invoices behind them by voucher number.
2. The map: get_object on the entries says they meet a payout only by date and amount, with no id both sides carry. The agent reads the payout’s balance transactions in Stripe with its own read access.
3. Findings: Where the last scan of the exports found payouts the entries do not add up to, a finding with its evidence and a recommendation.
4. The action gate: request_action for a task for the bookkeeper with the payout, what it is made of in Stripe, and the date and amount to look for in e-conomic’s entries.
5. Record and value: record_action records that the task went out, and what the bookkeeper found.

Result: The bookkeeper checks the payout against e-conomic’s entries with Stripe’s side of it already broken down.