Quasar Docs

E-Invoicing & Compliance

Received Supplier Documents

The Received Supplier Documents report displays inbound electronic tax documents (ETDs) received from vendors for reconciliation and processing. It queries the received_etd table and provides filtering by supplier, document type, status, date range, and store. Documents can be inspected, item-matched, and converted into Quasar Vendor Invoices (Receive transactions) directly from this screen. Access from Setup › Purchases › Received Supplier Docs.

Filter Fields

FieldDescription
Supplier TINFilter by the supplier's Tax Identification Number. Exact match.
ETDUIFilter by the Electronic Tax Document Unique Identifier. Exact match on the full 44-character ETDUI.
StatusFilter by document processing status:
All Statuses — Show all documents
Received — Document received but not yet processed
Processed — Document has been converted to a Vendor Invoice
Disputed — Document flagged for dispute
ETD TypeFilter by document type:
All Types — Show all
01 - Invoice — Standard supplier invoice
02 - Tax Receipt — Official receipt/acknowledgement
03 - Debit Note — Additional charge from supplier
04 - Credit Note — Credit/adjustment from supplier
RangePre-set date range for the Received Date. Defaults to “Today”.
FromStart date filter on Received Date.
ToEnd date filter on Received Date.
StoreFilter by store. Defaults to the current store.

Status, ETD Type, date range, and store filters auto-refresh the report when changed.

Report Columns

Columns can be shown/hidden and reordered using the Columns... button. Configured column layouts are persisted.

ColumnDescription
ETDUIElectronic Tax Document Unique Identifier (44 characters). Globally unique document key.
StoreName of the store this document was received for.
Trans #The supplier's invoice/transaction number.
Supplier TINTax Identification Number of the issuing supplier.
Supplier NameBusiness name of the issuing supplier.
ETD TypeDocument type code (01=Invoice, 02=Tax Receipt, 03=Debit Note, 04=Credit Note).
Issue DateDate the supplier issued the document.
TotalDocument total amount.
CurrencyISO currency code (e.g., PHP, USD).
StatusProcessing status: Received, Processed, or Disputed.
Event CodeClient event code from the e-invoicing system.
ReceivedDate the document was received into Quasar.
MethodDelivery method code (how the document was received).
MismatchesCount of line items with no product match. Uses a 3-tier matching strategy:
Tier 1: vendor_item_map (vendor-specific item mapping)
Tier 2: item_num (direct item number match)
Tier 3: No match — counted as a mismatch
Returns -1 if the XML cannot be parsed.

Document List

The list of received supplier documents matching the current filters. Double-click any row to open the detail view.

Double-click any row to open the Received ETD Detail view, which shows the full document XML, resolved line items, and processing options.

Totals Summary

FieldDescription
Row CountTotal number of documents in the filtered results.
Total AmountSum of all document totals in the filtered results.

Actions

ButtonDescription
RefreshRe-queries the received_etd table with current filter settings.
Process SelectedProcesses the selected document(s) by parsing the UBL XML, resolving line items, and opening a Vendor Invoice (ReceiveMaster) for each. Supports multi-select.
PrintGenerates a printable report with title lines showing all active filters and date range.
Columns...Opens the column configuration dialog to show/hide and reorder columns. Layout is persisted between sessions.
CloseCloses the report window.

Item Matching Logic

The Mismatches column uses a 3-tier resolution strategy to determine how many line items in the UBL XML document can be matched to Quasar inventory items:

Tier 1 — Vendor Item Map: Looks up the SellersItemIdentification/ID from the XML against the vendor_item_map table for the matched vendor (resolved by Supplier TIN).

Tier 2 — Direct Item Number: If Tier 1 fails, checks the item_num table for a direct match on the seller's item number.

Tier 3 — Mismatch: If both tiers fail, the line is counted as a mismatch, indicating manual mapping may be needed before processing.

If the BuyersItemIdentification is present but SellersItemIdentification is not, the buyer's ID is used as a fallback.

Related Screens

PAC Cert Report Vendor Invoice

Quasar Accounting 7.1 • © Linux Canada Inc. • Table of Contents