Table 3303 "Payables Agent Setup"
PayablesAgent · Microsoft.Agent.PayablesAgent
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 5 connected objects and pages
PayablesAgent · Microsoft.Agent.PayablesAgent · BC29-30 · source at ea08af5e · facts from BC29
Learn documents this table through its pages: Page 3304 “Payables Agent Setup” (2 Learn pages).
Properties
| Property | Value |
|---|---|
| Access | Internal |
| Extensible | false |
| Permissions | tabledata “Payables Agent Setup” = ri |
Fields
Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.
| No. | Name | Type | Explanation | Notes |
|---|---|---|---|---|
| 1 | Id | Integer | — | DataClassification SystemMetadata |
| 2 | E-Document Service Code | Code[20] | — | TableRelation Table 6103 “E-Document Service” (“E-Document Service”.Code); DataClassification CustomerContent |
| 3 | Monitor Outlook | Boolean | Specifies whether the agent should monitor incoming emails for PDF document attachments for processing. via Page 3304 “Payables Agent Setup” | DataClassification SystemMetadata |
| 4 | Agent User Security Id | Guid | — | obsolete Pending 28.0; #if not CLEANSCHEMA28; DataClassification SystemMetadata |
| 5 | Review Incoming Invoice | Boolean | — | DataClassification CustomerContent |
| 7 | Exists | Boolean | — | FlowField: exist(Agent where(“User Security ID” = field(“User Security Id”))) |
| 9 | Last Activated | DateTime | — | DataClassification SystemMetadata |
| 10 | User Security Id | Guid | — | DataClassification SystemMetadata |
| 11 | Use MLLM Processing | Boolean | Specifies whether the agent should use MLLM for document processing. via Page 3311 “PA MLLM Setup” | obsolete Pending 29.0; #if not CLEANSCHEMA32; DataClassification SystemMetadata |
| 12 | Email Review Policy | Enum “PA Email Review Policy” | Specifies when the agent should request human review before processing an incoming email. ‘Manage per sender’ skips review for previously approved senders and any email that arrives in a configured subfolder. via Page 3304 “Payables Agent Setup” | enum Enum 3305 “PA Email Review Policy”; DataClassification CustomerContent |
| 13 | Applied Instr. Config Hash | Text[64] | Applied Instructions Configuration Hash caption | DataClassification SystemMetadata |
Keys
- PK: Id (clustered)
Procedures
GetSetup()(internal)GetSetup(InsertIfMissing: Boolean): Boolean(internal): Gets the setup and optionally creates it if missing
Relations
- E-Document Service Code: TableRelation Table 6103 “E-Document Service”
Pages and codeunits on this table
- Page 3304 “Payables Agent Setup” (source table)
- Page 3311 “PA MLLM Setup” (source table)
Recent changes
- 2026-08-19 #10253 Avoid starting a write transaction under
ShowCanCreateAgent(main, BC30, fix) - 2026-08-18 #7546 [Payables Agent] Agent-driven line matching (main, BC30, feature)
- 2026-07-22 #9635 Obsolete MLLM Payables Agent rollout scaffold (main, BC30, obsoletion)
Deprecations
- field Agent User Security Id: Pending 28.0 (#if not CLEANSCHEMA28), “No longer used, replaced by “User Security Id” field”
- field Use MLLM Processing: Pending 29.0 (#if not CLEANSCHEMA32), “The MLLM Payables Agent feature is fully rolled out; the toggle used to roll it out is no longer needed.”
Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).
Ask your agent
Procedure bodies are not stored here (D10). For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "table", object_name: "Payables Agent Setup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.