Table 3308 "PA Known Sender"

PayablesAgent · Microsoft.Agent.PayablesAgent · captioned “Payables Agent Known Sender” · BC29-30 · source at ea08af5e · facts from BC29

Learn documents this table through its pages: Page 3313 “PA Known Senders” (2 Learn pages).

Properties

Property	Value
Caption	‘Payables Agent Known Sender’, Comment = ‘Payables Agent is a term, and should not be translated.’
Access	Internal

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	BigInteger	—	AutoIncrement; DataClassification SystemMetadata
2	Email	Text[250]	Specifies the email address of a sender whose e-documents have been processed by the Payables Agent.	DataClassification EndUserIdentifiableInformation
3	Sender Policy	Enum “PA Sender Policy”	Specifies how an incoming email from this sender is handled. ‘Ask’ requests human review. ‘Approve’ processes without review (effective when overall email review is ‘Manage per sender’). ‘Reject’ ignores the email.	enum Enum 3307 “PA Sender Policy”; DataClassification CustomerContent

Keys

PK: Id (clustered)
Key1: Email

Procedures

InsertIfNew(EDocument: Record "E-Document") (internal)
GetForEDocument(EDocument: Record "E-Document"; var KnownSender: Record "PA Known Sender"): Boolean (internal): Finds the known-sender record matching the e-document’s sender, if any. Returns false when the sender is empty or not in the list.

Plus 2 local procedures.

Triggers

OnInsert, OnModify

Pages and codeunits on this table

Page 3313 “PA Known Senders” (source table)

Recent changes

2026-08-08 #10022 Known senders table should only be inserted to when the task is coming from an email (main, BC30, fix)
2026-07-30 #9805 Update Email Folder tooltip to reference renamed ‘Manage per sender’ review option (main, BC30, fix)

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: "PA Known Sender"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.