AP Automation Supplier Access Applet
Overview
The AP Automation Supplier Access Applet is the supplier’s window on the buyer’s AP Automation reconciliation. A user whose login is linked to a Consolidated Arap group in the buyer’s tenant opens it and sees only the e-Invoices that group’s suppliers issued, each with how it matched — or did not — against the buyer’s delivery notes and goods received notes. The supplier can type a Supplier Remark and set an Action Deadline on each row; everything else is read-only. The matching report the buyer’s finance team e-mails to suppliers points them here to explain unmatched cases.
It creates no document and changes nothing in the buyer’s ledger, stock or supplier balance. It writes two columns on the buyer’s tracking row.
The window title is AP Automation Supplier Access Applet.
Where it fits
| Position | Applet / document | Relationship |
|---|---|---|
| Module | Purchasing, E-Invoice | The supplier-facing half of the AP reconciliation |
| Buyer’s applet | AP Automation | The same bl_b2b_process_tracking_einvoice_hdr rows, filtered to the supplier’s group; the buyer’s Finance Remarks and Payment Status are visible here read-only, the supplier’s Supplier Remarks and Action Deadline are visible there read-only |
| Access | Supplier → Consolidated Arap → its login links (bl_fi_consolidated_arap_login_subject_link) | Not the Supplier Login tab the other supplier-access applets use. Every query in this applet resolves the signed-in subject to the Consolidated Arap groups it is linked to, then to the supplier entities in those groups; a login linked to no group is refused |
| Siblings | Purchase Order Supplier Access, Purchase GRN Supplier Access | The buyer’s orders and receipts, through the Supplier Login link |
Screens and menus
| Menu | Route | What it is |
|---|---|---|
| E-invoice Summary | einvoice-summary | One row per e-Invoice of type 01 issued by a supplier in the login’s group: Supplier Name, E-invoice No, E-invoice Date, E-invoice Amount, Purchase Order No, Delivery Order No, Validation Datetime, LHDN unique no, Source, Supplier Remarks. Advanced search by supplier name |
| B2B vs E-invoice Summary | b2b-einvoice-summary | The reconciliation grid for the group’s suppliers: the e-Invoice header beside the buyer’s matched delivery-note / GRN lines, amount difference, document and value matching, remarks, action deadline, payment status |
| Settings | settings/… | Field Settings (renders nothing — see below), Default Selection, Webhook, Client Side Permission, Permission Set / User / Team / Role Permission |
| Personalization | personalization/… | Personal Default Selection, Sidebar |
There are no HIDE_…_MENU settings; the two menus are fixed.
Opening a row on either screen shows Main Details with the e-Invoice and matching fields read-only and two editable controls — Supplier Remarks and Action Deadline — plus Save. On the B2B vs E-invoice screen the Purchase Order, Delivery Order and GRN tabs show the buyer’s matched documents read-only.
Configuration
Before you can use it
| Prerequisite | Where | Why |
|---|---|---|
| A Consolidated Arap group containing the supplier entity or entities, whose account name is the supplier’s name as printed on its e-Invoices (or whose account code appears inside that name) | Supplier → Consolidated Arap | The group is the unit of access, and it holds no amounts. When the buyer’s matcher records an e-Invoice it looks the group up by the e-Invoice supplier name — trigram similarity > 0.8 to the group’s account name, upper-cased, or the name containing the group’s code — and stamps the row with that group. A row that found no group, or more than one, carries none and is invisible in this applet and refused on update, however the login is linked |
| The supplier user’s login linked to that group | Supplier → Consolidated Arap → the group’s login links | Every endpoint this applet calls is the login-consolidated-arap-ep variant, which reads bl_fi_consolidated_arap_login_subject_link for the signed-in subject and refuses when nothing is linked |
| The buyer’s AP Automation processors running | Buyer’s tenant | This applet only reads rows those processors create |
| The applet granted to the supplier’s login | Buyer’s tenant administration | As for any supplier-access applet |
Applet settings
Field Settings exists on the menu and in the routes, but it is a mock: the template shows a Lines Settings panel of slide toggles (Unit Discount, SST/VAT/GST, WHT and others) bound to no form control, and a SAVE button wired to nothing. Its component declares no controls and no save handler. Flipping a toggle changes nothing and is not stored.
Default Selection — DEFAULT_BRANCH, DEFAULT_LOCATION, DEFAULT_COMPANY,
DEFAULT_TIMEZONE: declared, rendered and saved, and read by no listing in this applet. Setting
them changes nothing visible today.
Document behaviour settings
Not applicable — no document.
Settings in other applets that control this applet
| Setting | Where it is set | Effect here |
|---|---|---|
| Consolidated Arap groups and login links | Supplier | Decide which suppliers’ rows a login sees, and whether it sees anything |
Supplier name aliases (EINVOICE_MATCHING_SUPPLIER_NAME_ALIAS) | Tenant configuration, no screen | Decide whether the supplier’s e-Invoices matched at all — see the buyer’s applet page |
Feature visibility / permissions
The code checks no client-side permission. bl_applet_client_side_perm_dfn holds zero rows for
APAutomationSupplierAccess (queried 2026-09-15). Server-side, the login-consolidated-arap-ep
endpoints substitute the group membership for a permission check: the subject’s linked groups are
resolved and the query is restricted to those groups’ supplier entities; no API_TNT_DM_…
permission is evaluated on the read or the update.
Fields
Main Details
| Field | Meaning | Editable | Notes |
|---|---|---|---|
| Supplier Name, E-invoice No, E-invoice Date, E-invoice Amount, Delivery Order No, Validation Datetime, LHDN unique no, Source | The e-Invoice as the buyer’s OCR or Peppol reception recorded it | No | |
| Document Matching Status, Value Matching Status | M / UM from the buyer’s matcher | No | |
| Payment Status | PENDING / PAID, set by the buyer’s finance team | No | |
| Supplier Remarks | Free text | Yes | The supplier’s explanation of an unmatched or under-valued row |
| Action Deadline | Date | Yes | Also editable by the buyer |
| Finance Remarks | The buyer’s note | No (B2B vs E-invoice screen) |
Lifecycle and effects
No document, no statuses, no posting. Save on either screen sends the row through the
login-consolidated-arap-ep update endpoint, which re-checks the login’s group membership and
writes supplier_remarks and action_deadline on bl_b2b_process_tracking_einvoice_hdr. The
buyer’s finance team sees the change in their B2B vs E-invoice Summary on the next load; nothing is
e-mailed on save.
The buyer’s matching report (an Excel file e-mailed to every login linked to the group) is what brings a supplier here; the applet itself sends nothing.
Posting proof. Server document type: none. Signums: not applicable. Dr / Cr equation: none. Stock processor: none. VOID: none.
Related applets
- AP Automation — the buyer’s applet and the full description of how a row gets its matching statuses.
- Supplier — the Consolidated Arap groups and login links that decide what a supplier sees.
- Purchase Order Supplier Access and Purchase GRN Supplier Access — the buyer’s orders and receipts, seen through the Supplier Login link rather than a Consolidated Arap group.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| The supplier signs in and every screen is empty or refused | The login is linked to no Consolidated Arap group, or the group contains no supplier entity | Link the login on the Supplier applet’s Consolidated Arap screen, and put the supplier entity in the group |
| The login is linked, the e-Invoices exist in the buyer’s summaries, and the supplier still sees nothing | The rows carry no group: the group’s account name was not similar enough (> 0.8) to the supplier name on the e-Invoice, or its code does not appear in that name, so the matcher stamped nothing | Rename the group’s account name to the supplier’s e-Invoice name (or set its code to a distinctive fragment of it); rows are re-stamped when the matcher next updates them — a Reprocess in the buyer’s applet forces that |
| The supplier sees another company’s e-Invoices | The group contains more than one supplier entity | Expected — a group is a deliberate grouping of entities under one login. Split the group if that is wrong |
| An e-Invoice the supplier issued is missing | Only type 01 rows appear on E-invoice Summary; or the buyer’s OCR or Peppol feed has not picked it up yet | Check the type; allow the buyer’s hourly processors to run |
| Payment Status cannot be changed | It is the buyer’s field; read-only here | Expected |
| Save appears to do nothing | The update is refused when the login’s group membership no longer includes the row’s supplier | Re-link the login |
| Field Settings shows toggles that do not stick | The screen is a mock — no control is bound and SAVE does nothing | Expected; there is nothing to configure |
Related documentation
- Purchasing Module — the supplier’s window — how the seven supplier-access applets differ
- E-Invoice Module