An accounting system is the one place where a small mistake stays. A posted invoice cannot be quietly taken back. That is why TeamUP treats the actions on Business Central in three different ways.
Three levels of action
| Level | What an agent can do | Who decides |
|---|---|---|
| Read | Look up a customer, a balance, overdue invoices, an item's availability, a document with its lines. | Free: no approval needed. |
| Prepare | Create an unposted sales order or purchase invoice. | Follows the agent's mode: draft, gated or auto. |
| Post | Post an invoice, or ship and invoice an order. | A person approves it, unless an admin allowed it for that agent. |
Mistakes are caught before a document exists
Before a document is created, TeamUP checks that the customer or vendor exists, that every item exists and is not blocked, that quantities are above zero, and that there are at most 50 lines. A typo is reported instead of producing half a document.
Creating the same document twice is prevented too: a sales order with the same customer and external document number returns the one that already exists.
A repeated approval cannot post twice
Posting only posts a draft. An invoice that is already posted or paid is refused, so approving the same request twice does not post it twice.
Business Central keeps its own rules
TeamUP does not copy Business Central's data. Each question goes to Business Central, which applies its own permissions to the connection's account. What comes back is treated as data, never as instructions.
- Agents read freely and prepare unposted documents.
- Posting cannot be undone, so a person approves it.
- Checks run before a document is made, and a repeated approval does nothing.