Sales Report Supplier Access

Gives a supplier’s own login one report: how much of its items you sold, in which branch, over a date range, with a cost value beside it, so nobody has to export a spreadsheet and e-mail it. It reads the final lines of sales invoices, POS cash bills and sales returns, with returns subtracting, and it creates no document, posts nothing and moves no stock. Sales Cost is the price or cost basis you choose multiplied by the quantity, not a recorded cost of sale, so agree the basis with the supplier.

Your job, and the screen for it

Overview

It is a read-only report applet. It has one report screen, seven columns, and no second report. The one thing it writes is a setting: which branches each supplier is allowed to filter on.

Where it fits

Screens and menus

Opening the applet lands on the report screen; anything unmatched goes to a 404 page.

There is exactly one menu entry:

Settings has two entries: Application Settings (field-settings) and Supplier Settings (supplier-settings). Personalization lists two, but only Default Selection (personal-default-selection) opens — its Field Settings entry points at a screen that does not exist and falls through to the 404. Six further screens have no menu entry at all: webhook, release-notes and the four permission listings.

Sales Report

Seven columns:

There is no gross-profit, margin, inventory-turnover, sell-through-forecast or stockout column, and no screen that produces one.

The grid is ag-Grid with pagination, the side bar, row grouping (“Drag here to set row groups”), range selection and multi-row selection turned on, and Export PDF and Export XLS buttons above it.

Supplier Settings

Two columns. Supplier Listing lists suppliers — Supplier Code, Supplier Name, Description, Type, Phone — filtered to active suppliers and searched on code, name, phone and description. Clicking a row opens Add Branch Link for that supplier.

Add Branch Link is the branch whitelist editor: a multi-branch drop-down, ADD, Delete and SAVE, over a grid of Code and Name. Saving stores the list on the supplier record itself, as the supplier’s SUPPLIER_ACCESS_BRANCH setting — not in this applet — so it survives whatever happens to this applet and is visible from the supplier’s own record. The confirmation toast reads “Add Branch Link saved successfully”.

That whitelist is what the report’s Branch filter offers: the branch drop-down reads the login’s supplier links and takes the branch list from each linked supplier’s SUPPLIER_ACCESS_BRANCH setting.

Configuration

Before you can use it

• The supplier must exist as an entity flagged as a supplier, maintained in Supplier Applet.
• The supplier’s people must have BigLedger logins linked to that supplier entity. The link is written from the supplier record’s Login tab. Without it the applet is not scoped at all — a login with no entity link falls into the back-office path and sees every supplier, subject to the three permissions below.
• Item–supplier links with the supplier’s own code, if ALTERNATE CODE is to show anything: it comes from the item’s supplier pricing link.
• A branch whitelist per supplier, set in Supplier Settings, or the supplier’s Branch filter will be empty — and Branch is a required filter.

Applet settings

Where they live. Application Settings is this applet’s own settings screen, not the shared one other applets use. Supplier Settings is applet-local. Default Selection under Personalization is per-login.

Three toggles are rendered on the Sales Report Listing tab of Application Settings, each labelled with its raw key and each saved as an applet setting.

Personal Default Selection offers Default Branch and Default Location, saved per login. Nothing in the report screen reads either; they are inert in the same way.

Application Default Settings exists in the applet but has no route and no menu entry, so you will not find it on screen.

Settings in other applets that control this applet

Feature visibility / permissions

The applet declares no permissions of its own. The backend defines three:

They are evaluated only when the login has no supplier link. For an actual supplier user none of the three is ever checked. Granting them to a supplier changes nothing; withholding them from a supplier blocks nothing.

The Add Branch Link screen checks nothing of its own — reaching the applet’s Settings area, and the backend’s own authorisation on reading and updating the supplier record, are the only controls on who may edit a supplier’s branch whitelist.

Fields

The report has no form. Its inputs are the advanced-search filters:

Calculate Base On offers fourteen bases: replacement cost, reference price 1–3, delta price 1–3, rebate price 1–3, sales minimum and maximum price, and purchase minimum and maximum price.

Date and Month are mutually exclusive — ticking both is refused (see Troubleshooting).

Lifecycle and effects

This is a report applet. It creates no document, posts no journal and moves no stock. There is no server document type of its own; it reads other documents’ lines.

What it reads. One report query, taking the selected branches, the keyword and the date range. The response comes back as a single stream rather than in pages, which is why the applet counts the rows itself.

How the rows are chosen: document lines that are FINAL, whose transaction date falls in the range (the end date is included), that are not forex-linked, and that belong to a POS cash bill, a sales invoice or a sales return. Those are exactly the three sales document types that move quantity — cash bill and invoice one way, return the other — so a quotation, an order or a delivery order never appears here, and a return subtracts from QTY SOLD rather than adding.

The supplier scoping, exactly:

1. The report looks up the supplier entities the logged-in user is linked to (active links only).
2. If it finds any, the permission check is skipped outright, and the query is narrowed to those suppliers.
3. If it finds none, the three permissions above are checked instead, and the query is not narrowed: every active supplier is returned.

So an unlinked login with one of the three permissions sees every supplier, and a linked login sees only its own — regardless of permissions. That is the behaviour to check first when a supplier reports seeing too much or too little.

What it writes. The supplier branch whitelist (onto the supplier record), the applet settings from Application Settings, and the login’s personal settings from Default Selection. The advanced-search component also saves the current filter state as a personal setting on every search. Nothing else.

Related applets

• Supplier Applet — where the supplier entity and, crucially, the login link are maintained. Everything this applet does hangs off that link.
• Sales Report — the internal sales reporting applet, with the full column set and no supplier scoping.
• Sales Invoice (Internal), POS General, Sales Return (Internal) — the three document types whose FINAL lines this report sums.
• Supplier Delivery Order, Purchase Order Supplier Access, Purchase GRN Supplier Access, Purchase Invoice Supplier Access — the rest of the supplier-facing set, scoped by the same login link.
• Organisation — the branches the whitelist is drawn from.

Troubleshooting

Related documentation

• POS and Sales module
• Supplier Applet — the Login tab that makes supplier access work.