Skip to main content
The Accounting Routes page of the Bank Transfer plugin binds each organization, ledger, and transfer type to the Midaz accounting routes that the plugin posts with. The combination of organization, ledger, and transfer type is a scope. You create the routes in Midaz. This page only brings them in. See Managing accounting routes. Each Bank Transfer screen needs the bank-transfer permission: get to see it, post to act on it, patch to change settings and the routing document, and delete to delete a webhook.
The plugin has no fallback route. It refuses the outgoing transfers of a scope without a binding. It holds the incoming credits of that scope, and does not return them on its own.

​
Accessing the page

1

Open Bank Transfer

From the Midaz Module sidebar, expand Bank Transfer.
2

Click Accounting Routes

Select Accounting Routes in the submenu.
The page has two parts: Cutover readiness at the top, and Bindings below it.

​
Cutover readiness

Cutover readiness is the report of the plugin on the stored bindings. The plugin reads Midaz back to check that the routes of each binding exist. The panel shows the state of the stored document: Never written, Not migrated, Written, no bindings, or Written. When the plugin still holds initiations frozen before ledger routing existed, the panel counts them. The plugin refuses to process them, so start them over.

​
Coverage by scope

The label Required for chargeback refunds marks the inbound scope that a ledger with outgoing transfers needs for chargeback refunds. If the plugin cannot produce the report, the panel says so. The bindings below still show what is stored, but nothing confirms that their routes exist. This message is not an all-clear.

​
Bindings

The Bindings table shows the stored document. A tenant holds at most 100 bindings. Instead of the table, the page can show one of these states:

​
Add or edit a binding

Your edits stay on the page until you save. A save replaces the whole document.
1

Open the binding form

Click Add binding. To change a binding, click the edit icon () on its row.
2

Choose the scope

Select the Organization, the Ledger, and the Transfer type. When you edit a binding, you cannot change its scope. To move a binding, remove it and add another.
3

Choose the mode

In Mode, keep Posts with routes, or select Posts without routes.
4

Choose the routes

With Posts with routes, select the Transaction route, then the Source operation route and the Destination operation route. Each leg lists the operation routes of its direction, plus the routes that serve both directions. To type an id that a list does not show, click Enter id by hand on that field.
5

Save the document

Click Save in the form. The binding goes into your draft. Then click Save on the page to send the document to the plugin. To drop your edits, click Discard.
Posts without routes sends the transfers of the scope with no accounting routes. Midaz accepts them only while route validation is off on the ledger. With validation on, Midaz refuses every transfer of the scope. The form asks you to confirm this mode.

​
Remove a binding

Click the remove icon () on the row, confirm with Remove binding, then click Save. After the save, the scope is uncovered. The plugin refuses its outgoing transfers and holds its incoming credits.

​
When someone else saved first

If another person saved the document after the page read it, the page shows Someone else saved this document first. Click Reload and discard my changes to read the stored document, then make your change again.

TED IN operations

Inspect retained inbound messages and record where the money went.

Managing accounting routes

Create the Midaz routes that a binding names.