BEAT: Beyond ERP Atlas Test

saved

Charts of accounts - all

Path: General ledger > Chart of accounts > Accounts > Chart of accounts

Observed menu item: LedgerChartOfAccounts

Chart BEAT with ten saved synthetic accounts for AP, AR, inventory, accruals, sales, expenses, equity and test cash clearing.

saved

Fiscal calendars

Path: General ledger > Ledger setup > Fiscal calendars

Calendar BEAT, fiscal year 2026, monthly operating periods.

saved

Currencies

Path: General ledger > Currencies > Currencies

USD, US Dollar, symbol $. Capture shows general and purchase rounding 0.01, sales rounding 0.00; Normal rounding method. Prices rounding 0.0000.

historical

Ledger: initial setup (historical)

Path: General ledger > Ledger setup > Ledger

Observed menu item: Ledger

Historical capture before structure assignment: chart BEAT, calendar BEAT, accounting currency USD and exchange rate type Default. See the later configured-ledger evidence for completed structure assignment and period recalculation.

saved

System parameters

Path: System administration > Setup > System parameters

Previously empty system-wide System language set to en-US and saved after account-structure creation reported that the language was unspecified.

resolved prerequisite

Account structures: prerequisite error

Path: General ledger > Chart of accounts > Structures > Configure account structures

Historical failure: System language is not specified. The language correction is recorded separately; this screenshot does not prove activation success.

active

Account structures

Path: General ledger > Chart of accounts > Structures > Configure account structures

BEAT-MAIN is Active, with MainAccount as the single segment and * as the allowed main-account criterion. No additional dimensions are required for this synthetic baseline.

saved

Ledger: structure assigned

Path: General ledger > Ledger setup > Ledger

Observed menu item: Ledger

BEAT-MAIN assigned to BEAT. Ledger period recalculation returned Operation completed. Chart BEAT, calendar BEAT, accounting currency USD and exchange rate type Default are saved.

observed

Ledger calendars: October

Path: General ledger > Ledger setup > Ledger > Ledger calendar

Selected Period 10, 1 October–31 October 2026: Operating, Open, module access <All>. Opening period remains permanently closed; no period status was changed.

saved

Terms of payment

Path: Accounts payable > Payment setup > Terms of payment

NET30, Atlas net 30 days, Payment method Net, Months 0, Days 30. Saved and read back; document due-date behavior not yet tested.

saved

Vendor posting profiles

Path: Accounts payable > Setup > Vendor posting profiles

Observed menu item: VendPosting

BEAT, Account code All, summary account 210100. Saved and read back.

saved

Customer posting profiles

Path: Accounts receivable > Setup > Customer posting profiles

Observed menu item: CustPosting

BEAT, Account code All, summary account 120100. Saved and read back.

saved

Vendor groups

Path: Accounts payable > Vendors > Vendor groups

Observed menu item: VendGroup

BEAT, Atlas synthetic suppliers, terms NET30.

saved

Customer groups

Path: Accounts receivable > Setup > Customer groups

BEAT, Atlas synthetic customers, terms NET30. Saved and read back.

saved

AP parameters: default posting

Path: Accounts payable > Setup > Accounts payable parameters > Ledger and sales tax

Observed menu item: VendParameters

Default Posting profile BEAT, saved and read back. Document defaults and voucher posting remain to be tested.

saved

AR parameters: default posting

Path: Accounts receivable > Setup > Accounts receivable parameters > Ledger and sales tax

Default Posting profile BEAT, saved and read back. Document defaults and voucher posting remain to be tested.

observed

AR parameters: number sequences

Path: Accounts receivable > Setup > Accounts receivable parameters > Number sequences

BEAT-only wizard proposals generated after removing temporary proposals whose format did not contain BEAT-. Customer account Acco_3, free text invoice Acco_11 and free text invoice voucher Acco_39 read back. Other companies were excluded from generation.

saved

All vendors: synthetic supplier

Path: Accounts payable > Vendors > All vendors

Atlas Demo Supplier saved in BEAT, supplier group BEAT, language en-US, currency USD. NET30 inherited from the group. Synthetic record only.

saved

All customers: synthetic customer

Path: Accounts receivable > Customers > All customers

Atlas Demo Customer saved in BEAT, customer group BEAT, language en-US, currency USD. NET30 inherited from the group. Synthetic record only.

saved

Units: ea

Path: Organization administration > Setup > Units > Units

ea, Each, Quantity class, decimal precision 0, Base unit Yes. Shared unit saved.

saved

Sites: BEAT

Path: Inventory management > Setup > Inventory breakdown > Sites

BEAT, Atlas test site, UTC time zone. Saved BEAT-company site.

saved

Warehouses: BEAT

Path: Inventory management > Setup > Inventory breakdown > Warehouses

BEAT, Atlas test warehouse, site BEAT, type Default. Use warehouse management processes No; physical/financial negative warehouse inventory No.

saved

Item model groups: receipt and delivery controls

Path: Inventory management > Setup > Inventory > Item model groups

BEATFIFO, Atlas stocked FIFO test. Stocked product, physical and financial inventory posting and receipt accrual enabled. Physical and financial negative inventory No; Receiving requirements and Deduction requirements Yes. Saved and read back.

saved

Item groups: sales posting

Path: Inventory management > Setup > Inventory > Item groups > Sales order

BEAT: cost of units delivered/invoiced 130100, cost of goods sold delivered/invoiced 510100, Revenue 410100. Saved setup, effective posting untested.

saved

Item groups: purchase accrual

Path: Inventory management > Setup > Inventory > Item groups > Purchase order

BEAT: Purchase, accrual 220100. Receipt and invoice mappings are listed in the execution log; effective posting untested.

saved

Item groups: purchase expense

Path: Inventory management > Setup > Inventory > Item groups > Purchase order

BEAT: Purchase expenditure for expense 610100. Discount, fixed-price, tax and prepayment accounts left outside baseline.

saved

Storage dimension groups

Path: Product information management > Setup > Dimension and variant groups > Storage dimension groups

BEATSTD, Atlas site and warehouse test. Site and Warehouse active, both tracked physically; financial inventory at Site. Warehouse Mandatory and Primary stocking Yes, blank receipts/issues No, WMS processes No.

saved

Tracking dimension groups

Path: Product information management > Setup > Dimension and variant groups > Tracking dimension groups

BEATNONE, Atlas no batch or serial test. Batch number, Serial number and Owner dimensions inactive; capture serial number None. Saved group for the basic stocked-item scenario.

saved

Released product details: BEAT-ITEM-001

Path: Product information management > Products > Released products

Observed menu item: EcoResProductDetailsExtendedGrid

BEAT-ITEM-001, Atlas Demo Stocked Item. Item/Product, BEATFIFO, BEATSTD, BEATNONE; item group BEAT; ea inventory/purchase/sales/BOM units. Purchase price 100 USD, sales price 150 USD, inventory price 100 USD. Synthetic baseline without sales tax.

validated

Released product validation

Path: Product information management > Products > Released products > Product > Validate

Observed menu item: EcoResProductDetailsExtendedGrid

System reports: All field values required for validation are specified for product BEAT-ITEM-001. Validation does not prove receipt, invoice or settlement posting.

saved

Shared Alerts prerequisite sequence

Path: Organization administration > Number sequences > Number sequences > Area: Alerts

Aler_1, format ######, range 1–999999, next 1. Generated only the missing Alerts Rule ID reference after InventParameters failed with that prerequisite error. Shared scope, not a BEAT transaction sequence.

saved

Inventory parameters: physical ledger posting

Path: Inventory management > Setup > Inventory and warehouse management parameters > Inventory accounting

Observed menu item: InventParameters

Post product receipt in ledger Yes; Post packing slip in ledger Yes; Post physical sales tax No. Saved and read back in BEAT.

resolved prerequisite

Purchase line prerequisite error

Path: Procurement and sourcing > Purchase orders > All purchase orders > Lines

Observed menu item: PurchTableListPage

Historical capture; the prerequisite was subsequently resolved. BEAT-000001 purchase header created. Initial BEAT-ITEM-001 line save blocked: System trade line number increment is not specified. Approved-vendor policy also warned; neither warning nor error proves a successful line save.

saved

System trade-line number prerequisite

Path: System administration > Setup > System parameters > General

System line number Increment corrected from 0 to 1 after purchase line save was blocked. Shared system setting. No other system options changed in this correction.

saved

Approved vendor list for test item

Path: Product information management > Products > Released products > Purchase > Approved vendor > Setup

BEAT-ITEM-001 approves supplier BEAT-000001 effective 6 October 2026, expiration Never. Saved and read back; approved-vendor policy remains Warning only.

confirmed

Confirmed test purchase order

Path: Procurement and sourcing > Purchase orders > All purchase orders > Purchase > Confirmation

Observed menu item: PurchTableListPage

BEAT-000001, supplier BEAT-000001, 10 ea BEAT-ITEM-001 at 100 USD; Approval status Confirmed and Operation completed. Receipt and invoice remain unposted.

saved

Supplier payment journal name

Path: General ledger > Journal setup > Journal names

Observed menu item: LedgerJournalSetup

BEAT-AP Vendor disbursement, currency USD, ledger offset 110100, voucher series Acco_116. No payment posting yet.

resolved prerequisite

Invoice blocked by inactive dimensions

Path: Procurement and sourcing > Purchase orders > All purchase orders > Invoice > Invoice

Observed menu item: PurchTableListPage

Historical capture; the prerequisite was subsequently resolved. BEAT-INV-001 quantity default/save blocked by inactive dimensions. This is a setup error, not a passed invoice-before-receipt test.

resolved prerequisite

Dimension activation prerequisite

Path: General ledger > Chart of accounts > Dimensions > Financial dimensions

Observed menu item: DimensionDetails

Historical capture; the prerequisite was subsequently resolved. Opening page explicitly reports dimension activation not completed and requires maintenance mode. Temporary maintenance servicing requested in PPAC.

completed

Financial dimension activation completed

Path: General ledger > Chart of accounts > Dimensions > Financial dimensions > Activate all

Observed menu item: DimensionDetails

Activation execution reports Operation completed in maintenance mode. Initial prerequisite failure is preserved separately. Normal-access restoration and invoice consumption verification remain pending.

verified prerequisite

Invoice quantity selection works after activation

Path: Procurement and sourcing > Purchase orders > All purchase orders > Invoice > Invoice > Default from

Observed menu item: PurchTableListPage

Default quantity for lines dialog opens without inactive-dimension error after activation. Ordered-quantity selection is available. This proves prerequisite resolution, not receipt/invoice posting.

verified setup

Configure account structures: BEAT-MAIN Active

Path: General ledger > Chart of accounts > Structures > Configure account structures

Observed menu item: DimensionConfigureAccountStructure

Fresh 2026-10-07 capture shows BEAT-MAIN Active, MainAccount segment, with no error banner. This confirms the saved account structure, not transaction completion.

observed baseline

Purchase inventory transaction before receipt

Path: Procurement and sourcing > Purchase orders > All purchase orders > Lines > Inventory > Transactions

Observed menu item: PurchTableListPage

BEAT-000001 line BEAT-ITEM-001: Receipt Ordered, quantity 10 ea, physical and financial dates empty. No receipt or invoice posting is claimed.

prepared posting

Purchase receipt: verified posting inputs

Path: Procurement and sourcing > Purchase orders > All purchase orders > Receive > Product receipt

Observed menu item: PurchTableListPage

Ordered quantity, Posting Yes, print No, reference BEAT-PR-001, receipt date 2026-10-07, 10 ea at 100 USD, line net 1,000. Pre-post capture only.

posted receipt

Purchase receipt completed

Path: Procurement and sourcing > Purchase orders > All purchase orders > Receive > Product receipt

Observed menu item: PurchTableListPage

Operation completed; BEAT-000001 status Received after posting BEAT-PR-001 for 10 ea. Voucher reconciliation remains pending.

posted receipt

Posted product receipt journal

Path: Procurement and sourcing > Purchase orders > All purchase orders > Receive > Journals > Product receipt

Observed menu item: VendPackingSlipJournal

Journal records BEAT-PR-001 against PO BEAT-000001, date 2026-10-07. Posted via intercompany No.

balanced subledger

Product receipt subledger accounting

Path: Procurement and sourcing > Purchase orders > All purchase orders > Receive > Journals > Product receipt

Observed menu item: VendPackingSlipJournal

Subledger BEAT-000000001: 140100 debit 1,000; 610100 debit/credit 1,000 each; 220100 credit 1,000. Total debits/credits 2,000 USD. GL transfer remains unverified.

matched draft

Supplier invoice matched receipt lines

Path: Procurement and sourcing > Purchase orders > All purchase orders > Invoice > Invoice

Observed menu item: PurchTableListPage

BEAT-INV-001 against BEAT-PR-001: BEAT-ITEM-001 10 ea at 100 USD, line net 1,000; product receipt quantity match Passed and price match Passed. Invoice not yet posted.

verified totals

Supplier invoice totals

Path: Procurement and sourcing > Purchase orders > All purchase orders > Invoice > Invoice

Observed menu item: PurchTableListPage

BEAT-INV-001 totals: USD subtotal 1,000, invoice amount 1,000, charges/tax/discount/round-off 0. Posting remains pending.

posted invoice

Supplier invoice posting completed

Path: Procurement and sourcing > Purchase orders > All purchase orders > Invoice > Invoice

Observed menu item: PurchTableListPage

F&O reports vendor invoice posting complete for BEAT-000001, BEAT-INV-001; PO status Invoiced. Total previously verified 1,000 USD; payment and ledger reconciliation pending.

posted invoice

Posted supplier invoice journal

Path: Procurement and sourcing > Purchase orders > All purchase orders > Invoice > Journals > Invoice

Observed menu item: VendInvoiceJournal

BEAT-INV-001 dated 2026-10-07, voucher BEAT-110000000, USD 1,000, tax zero, due 2026-11-06. GL voucher transfer still requires verification.

balanced subledger

Supplier invoice subledger accounting

Path: General ledger > Periodic tasks > Subledger journal entries not yet transferred > View accounting

BEAT-000000002: debits/credits 4,000 USD. 130100 inventory debit 1,000; 210100 vendor credit 1,000; 140100 receipt reversal credit 1,000; 220100 accrual reversal debit 1,000. Expenditure entries offset. GL transfer not yet verified.

transferred queue cleared

BEAT subledger transfer queue cleared

Path: General ledger > Periodic tasks > Subledger journal entries not yet transferred

After Transfer now for BEAT-000000002, Not transferred grid is empty and Pending transfer is 0. Invoice GL voucher readback remains the next check.

verified gl posting

Supplier invoice general ledger voucher

Path: General ledger > Inquiries and reports > Voucher transactions

GL journal BEAT-000002 voucher BEAT-110000000 dated 2026-10-07: signed USD 210100 -1,000; 130100 +1,000; 220100 +1,000; 140100 -1,000; 610100 net 0. Current layer, year closed No. Financial inventory/AP and accrual reversal verified.

settlement marked

Supplier invoice marked for synthetic settlement

Path: Accounts payable > Payments > Vendor payment journal > Lines > Settle transactions

Invoice BEAT-INV-001 for 1,000 USD selected with Mark checked. Settlement amount -1,000; cash discount zero. Selection is preparation, not posted settlement.

validated

Supplier clearing journal validated

Path: Accounts payable > Payments > Vendor payment journal > Lines > Validate > Validate

Journal BEAT-000001 / BEAT-AP, voucher BEAT-140000000, vendor BEAT-000001 debit 1,000 USD; offset Ledger 110100. Journal is OK and Operation completed. No bank/payment file generated.

posted

Synthetic supplier payment journal posted

Path: Accounts payable > Payments > Vendor payment journal > Lines > Post

BEAT-000001 / BEAT-AP, voucher BEAT-140000000 debit 1,000 USD for vendor BEAT-000001 offset Ledger 110100. Operation completed; Number of vouchers posted to the journal: 1. Remaining balances and GL readback pending.

verified gl posting

Supplier settlement clearing general ledger voucher

Path: Accounts payable > Payments > Vendor payment journal > Lines > Voucher

GL journal BEAT-000003 / voucher BEAT-140000000, 2026-10-07: 210100 vendor balance +1,000 USD, 110100 cash clearing -1,000 USD. Current layer, year closed No. Balanced synthetic payment, no bank transfer.

verified settlement

Supplier invoice and payment have zero remaining balances

Path: Accounts payable > Vendors > All vendors > Transactions

BEAT-110000000 invoice BEAT-INV-001 and BEAT-140000000 payment both show Balance in transaction currency 0.00 USD, Balance 0.00, Last settlement and Closed date 2026-10-07.

verified settlement

Supplier settlement history reconciles invoice and clearing payment

Path: Accounts payable > Vendors > All vendors > Transactions > View settlements

BEAT-140000000 Payment +1,000 USD and BEAT-110000000 Purchase order BEAT-INV-001 -1,000 USD each settled 1,000 USD, balance 0.00, settlement/closed date 2026-10-07 in BEAT.

configured header

Synthetic sales order header

Path: Accounts receivable > Orders > All sales orders > New > General

Draft header showed Sales order BEAT-000001, customer/invoice account BEAT-000001, USD and intended site/warehouse BEAT. Order type Sales order explicitly selected instead of Journal. Draft site/warehouse and customer reference did not persist; line storage dimensions were later saved directly and are evidenced separately.

saved line

Four-unit synthetic sales line and storage dimensions

Path: Accounts receivable > Orders > All sales orders > BEAT-000001 > Lines > Line details > Product

BEAT-ITEM-001, quantity 4 ea, unit price 150 USD, net 600. Site and warehouse BEAT explicitly saved on line Product tab after required-dimension validation. Order remains Open order, no delivery/invoice yet.

passed negative control

Expected negative control: invoice blocked before delivery

Path: Accounts receivable > Orders > All sales orders > BEAT-000001 > Invoice > Generate Invoice

Quantity All, 4 ea / 600 USD before packing slip. Posting canceled with quantity cannot be invoiced because inventory transactions with status Deducted are insufficient. Order remains Open order. This is expected control evidence, not a completed invoice.

prepared

Synthetic four-unit packing slip prepared

Path: Accounts receivable > Orders > All sales orders > BEAT-000001 > Pick and pack > Post packing slip

Quantity All, posting Yes, print No; BEAT-ITEM-001 update 4 ea, net 600 USD, site BEAT. Typed customer reference BEAT-PS-001 did not persist; actual generated packing slip BEAT-000001 was subsequently verified.

posted journal

Posted synthetic packing slip journal

Path: Accounts receivable > Orders > All sales orders > BEAT-000001 > Pick and pack > Journals > Packing slip

Packing slip BEAT-000001 version BEAT-000001.1, ship date 2026-10-07; sales order Delivered after Operation completed. Customer packing slip number blank: typed draft reference BEAT-PS-001 did not persist. Actual generated number is authoritative.

verified delivery quantity

Packing slip confirms four units delivered

Path: Accounts receivable > Orders > All sales orders > BEAT-000001 > Pick and pack > Journals > Packing slip > Lines

BEAT-ITEM-001 line shows Ordered 4.00 and Delivered 4.00; Remaining quantity blank. Physical and financial voucher checks remain separate.

verified gl posting

Delivery general ledger voucher confirms 400 USD cost

Path: Accounts receivable > Orders > All sales orders > BEAT-000001 > Pick and pack > Journals > Packing slip > Vouchers

GL journal BEAT-000004 voucher BEAT-1000000 dated 2026-10-07: 510100 cost of goods sold delivered +400 USD, 130100 inventory delivered -400 USD. Current layer, year closed No. Four units at cost 100 each.

verified prepost totals

Sales invoice totals 600 USD and cost 400 USD

Path: Accounts receivable > Orders > All sales orders > BEAT-000001 > Invoice > Generate Invoice > Totals

Packing slip quantity 4 ea: subtotal/invoice 600 USD, exchange rate 1; tax, charges, discounts, rounding zero. Cost value 400 USD, margin 200 USD, contribution 33.33 percent. This is pre-posting evidence, not final ledger reconciliation.

posted journal

Posted synthetic customer invoice

Path: Accounts receivable > Orders > All sales orders > BEAT-000001 > Invoice > Journals > Invoice

Customer invoice BEAT-000002 dated 2026-10-07, invoice/customer account BEAT-000001, sales order BEAT-000001, voucher BEAT-10000001, invoice amount 600 USD. Order Invoiced after Operation completed. First invoice number was consumed by expected negative-control attempt; no duplicate posted invoice observed.

verified gl posting

Sales invoice general ledger reconciles AR and revenue

Path: Accounts receivable > Orders > All sales orders > BEAT-000001 > Invoice > Journals > Invoice > Voucher

GL BEAT-000005 / BEAT-10000001 dated 2026-10-07: AR 120100 +600 USD, revenue 410100 -600 USD. COGS 510100 invoiced +400/delivered -400; inventory 130100 invoiced -400/delivered +400. Delivery voucher already carries net 400 COGS/inventory credit; no double count. Current layer.

saved setup

BEAT customer clearing receipt journal setup

Path: General ledger > Journal setup > Journal names

BEAT-AR Atlas synthetic customer receipt, Customer payment, voucher series Acco_116 (same BEAT-scoped sequence as AP, allocates next unique voucher), USD, offset type Ledger account 110100; Details, Current layer, new voucher in connection with balance. Approval/workflow remain No in disposable synthetic baseline.

settlement marked

Customer invoice marked for full synthetic receipt settlement

Path: Accounts receivable > Payments > Customer payment journal > Lines > Settle transactions

Customer BEAT-000001 invoice BEAT-000002, voucher BEAT-10000001, amount 600 USD, due 2026-11-06. Mark checked, amount to settle 600 USD, cash discount zero. Preparation only; receipt not posted yet.

validated

Customer receipt validation passed

Path: Accounts receivable > Payments > Customer payment journal > Lines

Journal BEAT-000002 / BEAT-AR, voucher BEAT-140000001, credit 600 USD and offset Ledger 110100. Operation completed; Journal is OK.

posted

Synthetic customer clearing receipt posted

Path: Accounts receivable > Payments > Customer payment journal > Lines

Operation completed, Number of vouchers posted to the journal: 1. Receipt BEAT-140000001 credits customer BEAT-000001 for 600 USD; no external bank transfer.

verified gl posting

Customer receipt GL reconciles AR and clearing

Path: Accounts receivable > Payments > Customer payment journal > Lines

GL BEAT-000006 / BEAT-140000001 dated 2026-10-07: 120100 -600 USD and 110100 +600 USD, Current layer, year closed No.

verified settlement

Customer invoice and receipt have zero remaining balances

Path: Accounts receivable > Customers > All customers > Transactions > View settlements

Invoice BEAT-10000001 / BEAT-000002 and receipt BEAT-140000001 both balance 0.00 USD, closed and last-settlement dates 2026-10-07.

verified settlement

Customer full settlement reconciles invoice and receipt

Path: Accounts receivable > Customers > All customers > Transactions > View settlements

View settlements: receipt -600 USD, invoice +600 USD; each settled 600 USD, balance zero, closed 2026-10-07.

verified inventory

Final on-hand inventory is six units

Path: Inventory management > Inquiries and reports > On-hand list > Transactions

BEAT-ITEM-001 physical inventory, available physical, available for reservation and total available all 6.00 ea; reservations and incoming/outgoing quantities blank.

verified inventory

Financial inventory reconciles 1000 receipt and 400 issue

Path: Inventory management > Inquiries and reports > On-hand list > Transactions

Purchased 10 ea / cost +1000 USD and Sold -4 ea / cost -400 USD; physical and financial dates 2026-10-07. Net six units valued 600 USD.

verified gl posting

Product receipt GL confirms accrual transfer

Path: Accounts payable > Purchase orders > All purchase orders > Receive > Journals > Product receipt > Vouchers

GL BEAT-000001 / BEAT-100000000 dated 2026-10-07: 220100 -1000 USD and 140100 +1000 USD, Current layer, year closed No. Receipt subledger expenditure debit/credit net zero and do not appear as separate GL rows.

verified balances

Final BEAT trial balance reconciled

Path: General ledger > Inquiries and reports > Trial balance

Main account set, Current layer, calendar 2026: 110100 -400, 120100 0, 130100 +600, 140100 0, 210100 0, 220100 0, 410100 -600, 510100 +400, 610100 0 USD. Debit/credit totals 6400 each; balance zero. Create balances initialized standard reporting summaries after empty-sandbox warning; All legal entity context was fixed in the first initialization dialog.

negative control prepared

Unreceived purchase invoice control inputs

Path: Accounts payable > Purchase orders > All purchase orders > Invoice > Generate Invoice

Separate PO BEAT-000011 confirmed, one ea at 100 USD. Invoice BEAT-NEG-RECEIPT-001 date 2026-10-07, Ordered quantity one, receipt match Failed, price Passed, no receipt.

passed negative control

Expected negative control: invoice blocked without receipt

Path: Accounts payable > Purchase orders > All purchase orders > Invoice > Generate Invoice

Operation canceled Purchase invoice. Exact gate: item BEAT-ITEM-001 has three-way matching but no product receipts selected. Order remains Open/Confirmed, Invoice journal disabled. This proves matching gate, not independent inventory receiving requirement.

verified cleanup

Disposable negative-test invoice draft removed

Path: Accounts payable > Purchase orders > All purchase orders > Invoice > Pending invoices

BEAT-000011 pending invoice inquiry empty after deleting only BEAT-NEG-RECEIPT-001. Posted core supplier invoice remains intact.

verified cleanup

Negative control order canceled and confirmed

Path: Procurement and sourcing > Purchase orders > All purchase orders > BEAT-000011 > Purchase order > Cancel; Purchase > Confirm

Disposable one-unit control PO BEAT-000011 is Canceled and Confirmed. Pending invoice draft was removed; no receipt or invoice was posted.

observed

Invoice validation and line matching policy

Path: Accounts payable > Setup > Accounts payable parameters > Invoice validation

Matching validation Yes; three-way line matching; policy override Higher than company policy; discrepancies Allow with warning; automatic header update No; price totals None. Successful 1000 USD matched invoice and missing-receipt rejection are separate transaction evidence.

observed

Charges matching disabled

Path: Accounts payable > Setup > Accounts payable parameters > Invoice validation > Charges matching

Match charges No; charges tolerance 0.00 disabled. No charges discrepancy test was executed.

observed

Invoice totals matching disabled

Path: Accounts payable > Setup > Accounts payable parameters > Invoice validation > Invoice totals matching

Match invoice totals No, individual totals tolerances disabled at 0.00. This records current BEAT setup, not a demonstrated totals matching control.

observed

Vendor settlement defaults

Path: Accounts payable > Setup > Accounts payable parameters > Settlement

Automatic settlement No; penny difference and over/underpayment 0.00; partial-payment cash discounts No. Core payment explicitly marked and fully settled its invoice. Partial settlement and automatic settlement variants remain untested.

observed

Accounts payable number-sequence references

Path: Accounts payable > Setup > Accounts payable parameters > Number sequences

Visible BEAT references include vendor Acco_99, payment voucher Acco_116, internal receipt Acco_128, internal invoice Acco_132, receipt voucher Acco_140 and invoice voucher Acco_144. Successful posted transactions separately verify effective allocation; the image is not a test of every sequence.

configuration gap

Vendor methods of payment — configuration gap

Path: Accounts payable > Payment setup > Methods of payment

BEAT has no vendor methods of payment. The core demonstration used explicitly marked ledger-clearing payment journals. Bank file generation, bank instruments and external payment integration remain unconfigured and untested.

saved

Aging period definitions — BEAT30

Path: Accounts payable > Setup > Aging period definitions

Saved and refreshed BEAT30: 90+ (-1 Unlimited), 90/60/30 (each -30 Day), Current (0 Unlimited), Forward printing. Five periods; default indicators retained. Report execution is separate evidence.

observed

Vendor aging report — execution parameters

Path: Accounts payable > Inquiries and reports > Vendor aging report

Cutoff and aging date 2026-10-07, Due date criteria, BEAT30 selected through lookup, details Yes, zero accounts included, Screen destination.

verified transaction

Vendor aging report — zero settled balance

Path: Accounts payable > Inquiries and reports > Vendor aging report

Generated report for BEAT-000001 Atlas Demo Supplier: balance cutoff 2026-10-07, 90+/90/60/30/Current columns, total and grand total 0.00 USD. This tests reporting after full settlement; no overdue or collection scenario was executed.

observed

Customer aging report — execution parameters

Path: Credit and collections > Inquiries and reports > Customers > Customer aging report

2026-10-07 cutoff/aging date, Due date, actual BEAT30 lookup selection, period labels and details Yes, zero accounts included, Update collections status No.

verified transaction

Customer aging report — zero settled balance

Path: Credit and collections > Inquiries and reports > Customers > Customer aging report

BEAT-000001 Atlas Demo Customer report shows cutoff 2026-10-07, five BEAT30 buckets, total and grand total 0.00 USD. This verifies reporting after full settlement, not overdue collections.

configuration gap

Cash discounts — empty setup

Path: Accounts payable > Payment setup > Cash discounts; Accounts receivable > Payments setup > Cash discounts

Visible Cash discounts list is empty. Core BEAT terms NET30 and both settled payments used no cash discount. Discount setup and discounted settlement are not demonstrated.

configuration gap

Payment days — empty setup

Path: Accounts payable > Payment setup > Payment days; Accounts receivable > Payments setup > Payment days

Payment days list is empty. NET30 core demonstration has no weekday/monthday restriction; restricted payment-day and due-date adjustment variants remain unconfigured.

configuration gap

Payment schedules — empty setup

Path: Accounts payable > Payment setup > Payment schedules; Accounts receivable > Payments setup > Payment schedules

Visible payment schedules list is empty. Core NET30 invoices had one due date and were fully settled. Installment schedules and flexible-plan behavior remain unconfigured and untested.

saved draft

Free-text invoice — saved synthetic service line

Path: Accounts receivable > Invoices > All free text invoices > New

Saved draft for BEAT-000001 Atlas Demo Customer dated 2026-10-07, due 2026-11-06, USD NET30; one service line 300 USD, main account 410100. No inventory movement, charges or tax configured. Posting and correction are separate tests.

posted

Free-text invoice posted — BEAT-000001

Path: Accounts receivable > Invoices > All free text invoices > Post

Operation completed; invoice BEAT-000001 posted for synthetic customer BEAT-000001, 300 USD, dated 2026-10-07, NET30 due 2026-11-06, main account 410100. Accounting status Completed. Voucher verification and credit/settlement are pending.

saved

Reusable free-text template saved — BEAT-SERVI

Path: Accounts receivable > Invoices > All free text invoices > Invoice > Save to template

F&O reports Template BEAT-SERVI has been saved. Approved BEAT-SERVICE code was limited to ten characters by the form. Saved from synthetic 300 USD service invoice, revenue 410100, NET30. Creation from template and recurring-generation variants are separate tests.

verified template creation

Invoice created from BEAT-SERVI template

Path: Accounts receivable > Invoices > All free text invoices > Invoice > New from template

Created new draft from BEAT-SERVI for customer BEAT-000001 using customer defaults. Copied service description, main account 410100, quantity 1 and unit price/amount 300 USD; NET30 due 2026-11-06. The draft is subsequently used for a credit memo test; no recurring batch execution claimed.

saved

Customer reason codes — BEAT-CRED

Path: Accounts receivable > Setup > Customer reason codes

Created, saved and refreshed BEAT-CRED with default comment Synthetic BEAT credit test and Customer enabled. Menu navigation directly verified; credit-reference use is a separate transaction test.

in progress

Synthetic credit original invoice and reason

Path: Accounts receivable > Invoices > All free text invoices > Invoice > Credit invoicing

Original invoice BEAT-000001 / voucher BEAT-30000000 / 300 USD selected; reason BEAT-CRED, Synthetic BEAT credit test. This dialog is a setup/reference checkpoint; subsequent credit posting failed duplicate voucher validation and is not verified.

posted

Free-text service credit posted

Path: Accounts receivable > Invoices > All free text invoices > Invoice journal

BEAT-000003 / BEAT-40000002 posted 2026-10-07 for -300 USD, customer BEAT-000001. Fresh credit posted after clearing original-invoice reference that had caused duplicate voucher validation. Settlement and GL readback are separate evidence.

ready to post

Service invoice and credit marked for settlement

Path: Accounts receivable > Invoices > All free text invoices > Invoice journal > Transactions > Settlement > Settle transactions

Marked BEAT-000001 +300 USD and BEAT-000003 -300 USD, settlement balance zero, no cash discount. This is a pre-posting checkpoint; remaining balances require post-settlement readback.

settled

Service invoice and credit fully settled

Path: Accounts receivable > Invoices > All free text invoices > Invoice journal > Transactions > View settlements > View related

BEAT-000003 / BEAT-40000002 -300 USD and original BEAT-000001 / BEAT-30000000 +300 USD, each settled 300 USD with balance zero, settlement and closed dates 2026-10-07. Posting reference dialog was cleared; settlement establishes the document linkage. GL readback pending.

verified

Service invoice and settled credit — GL readback

Path: General ledger > Inquiries and reports > Voucher transactions

Current-layer GL journal BEAT-000013 / voucher BEAT-30000000: 120100 +300 USD, 410100 -300 USD. Credit GL BEAT-000014 / BEAT-40000002: 120100 -300 USD, 410100 +300 USD, dated 2026-10-07. Both documents settled; this capture verifies these two vouchers only.

verified

Trial balance after settled service invoice and credit

Path: General ledger > Inquiries and reports > Trial balance

Recalculated Current layer 2026, Operation completed: debit and credit 7000 USD each, net zero. Closing 110100 -400, 120100 0, 130100 +600, 140100/210100/220100 0, 410100 -600, 510100 +400, 610100 0. Service invoice and credit preserve the core closing balances.

failed test

Template-generated invoice posting failed

Path: Accounts receivable > Invoices > All free text invoices > Post > Message details

BEAT-SERVI-derived draft restored to positive quantity 1 x 300 USD, revenue 410100, NET30; original invoice and reason fields cleared. Posting canceled because voucher BEAT-10000001 is already used on 2026-10-07. No invoice posted. Creation/copy is verified; reusable posting remains failed and numbering diagnosis is pending.

posted

Fresh BEAT-SERVI invoice posted after session refresh

Path: Accounts receivable > Invoices > All free text invoices > New from template > Post

Fresh unchanged BEAT-SERVI-generated service invoice BEAT-000004 posted after reloading the F&O session, Accounting status Completed, 1 x 300 USD to 410100, NET30 due 2026-11-06. Prior duplicate-voucher failures are separate troubleshooting evidence; exact cache/numbering root cause remains unconfirmed. Credit/settlement of this additional test and GL readback pending.

failed test

Fresh template draft duplicate-voucher troubleshooting

Path: Accounts receivable > Invoices > All free text invoices > New from template > Post > Message details

Fresh unchanged BEAT-SERVI positive 300 USD draft initially failed with voucher BEAT-40000002 already used. After reloading the saved F&O session, the same draft posted as BEAT-000004 / BEAT-30000003. Failure retained as history; exact cache/numbering root cause remains unconfirmed.

failed test

Original-reference credit posting failure

Path: Accounts receivable > Invoices > All free text invoices > Post > Message details

Credit reference BEAT-000004 caused voucher BEAT-30000003 already used on 2026-10-07; posting canceled. Original-reference behavior remains unresolved; this is not positive setup evidence.

posted

Template verification credit posted

Path: Accounts receivable > Invoices > All free text invoices > Post

Credit BEAT-000005 posted -300 USD, 410100, quantity -1, Accounting Completed after clearing original invoice and reloading saved session. Invoice journal confirms voucher BEAT-40000004. Root cause of original-reference failure unconfirmed.

verified

Template test settlement selection

Path: Accounts receivable > Invoices > Invoice journal > Transactions > Settlement > Settle transactions

Only BEAT-000004 +300 and BEAT-000005 -300 USD marked; settlement balance zero. Point-in-time selection before posting.

verified

Template test invoice and credit settled

Path: Accounts receivable > Invoices > Invoice journal > Transactions > View settlements

BEAT-30000003 / invoice BEAT-000004 +300 and BEAT-40000004 / credit BEAT-000005 -300 USD both fully settled, zero balances, settlement and closed dates 2026-10-07.

configured

Vendor reason saved and refreshed

Path: Accounts payable > Setup > Vendor reasons

Observed menu item: VendReason

Observed menu path Accounts payable > Setup > Vendor reasons. BEAT-CRED / Synthetic BEAT credit test persisted with Vendor Yes after Save and Refresh. Shared existing reason now applies to customers and vendors. Vendor credit/correction application remains unexecuted.

verified

Template invoice and credit GL verified

Path: General ledger > Inquiries and reports > Voucher transactions

Current layer 2026-10-07: GL BEAT-000015 / BEAT-30000003 AR 120100 +300/revenue 410100 -300; GL BEAT-000016 / BEAT-40000004 AR -300/revenue +300 USD. Four rows reconcile the posted template test pair.

verified

Whole-ledger balance after template test

Path: General ledger > Inquiries and reports > Trial balance

Calculated 2026 Current Main account set, Operation completed. Debit and credit totals 7600 USD each, net zero. Closing clearing -400, AR/AP/accruals/expense zero, inventory 600, revenue -600, COGS 400 USD; matches core closings after both 300 USD invoice/credit extensions.

configuration gap

Customer payment methods before setup

Path: Accounts receivable > Payments setup > Methods of payment

Historical baseline: BEAT customer methods list was empty before BEAT-CASH creation. Core receipt journal had no method; bank-file/payment-gateway variants not verified.

configured

Customer ledger-clearing payment method saved

Path: Accounts receivable > Payments setup > Methods of payment

Observed menu item: CustPaymMode

Setup capture checkpoint before functional tests: BEAT-CASH / Atlas cash test saved and refreshed: Period Invoice, payment status None, payment type Other, Account type Ledger, payment account 110100, bridging No, No draft. Bank files/direct-debit/SEPA and transactions using this new method remain unexecuted. Subsequent bounded ledger-clearing posting and settlement tests passed; see later linked evidence.

configured

Vendor ledger-clearing payment method saved

Path: Accounts payable > Payment setup > Methods of payment

Observed menu item: VendPaymMode

Setup capture checkpoint before functional tests: BEAT-CASH / Atlas cash test saved and refreshed: Period Invoice, payment status None, payment type Other, Ledger payment account 110100, bridging No, No draft. Bank instruments/files and transactions using this new method remain unexecuted. Subsequent bounded ledger-clearing posting and settlement tests passed; see later linked evidence.

observed

AP document form general settings

Path: Accounts payable > Setup > Forms > Form setup > General

Observed menu item: VendFormletterParameters

Observed General settings: print euro amount No, totals First, sales tax specification None, separate exempt balance No. Print management available; actual generated/printed vendor document layout remains unexecuted.

observed

AP document invoice settings

Path: Accounts payable > Setup > Forms > Form setup > Invoice

Observed menu item: VendFormletterParameters

After Refresh: tax exempt number No, all displayed dimension flags unchecked/disabled including Site and Warehouse, include documents None. Attempts to select Site/Warehouse did not persist; no enabled dimension printing claimed. Printed document output remains unexecuted.

failed test

Document dimension access limitation

Path: Accounts receivable > Setup > Forms > Form setup

Observed menu item: CustFormletterParameters

Visible application message: read-only access does not support non-editable dimensions for displayed configuration. AP dimension selections also did not persist. Dimension editing unresolved; no changed print behavior claimed.

observed

AR document general settings observed

Path: Accounts receivable > Setup > Forms > Form setup > General

Observed menu item: CustFormletterParameters

Observed General defaults: Item number Our, include both name/description No, external description Overwrite, euro No, totals First, sales tax specification None, separate exempt No, dimensions After item number, direct notes attachment No. Actual printing and access-limited dimension editing remain unverified.

observed

AR free-text document settings

Path: Accounts receivable > Setup > Forms > Form setup > Free text invoice

Observed menu item: CustFormletterParameters

Free text invoice document settings: Blank paper, print tax-exempt number No, include document None, type blank. Existing posted free-text tests did not print invoice reports; rendering/layout and printed credit reference unverified.

observed

AR sales invoice document settings

Path: Accounts receivable > Setup > Forms > Form setup > Invoice

Observed menu item: CustFormletterParameters

Blank paper, packing-slip specifications unchecked, tax-exempt number unchecked, documents None, displayed dimension flags unchecked, backorder No tracking. Actual report rendering/printing remains unexecuted; dimension access limitation recorded separately.

observed

AR delivery document settings

Path: Accounts receivable > Setup > Forms > Form setup > Packing slip

Observed menu item: CustFormletterParameters

Blank paper, documents None, displayed dimension flags unchecked, shipping details unchecked, only-one-shipping-line unchecked, backorder No tracking, Save in print archive unchecked. Core delivery posted but printed document/archive output remains unexecuted.

configured

Free-text report Screen destination saved

Path: Accounts receivable > Setup > Forms > Form setup > General > Print management > Free text invoice > Original

FreeTextInvoice.Report, Original, default setting, one copy, Suspend printing No. Printer destination was Unavailable; selected Screen and Save in print archive Yes, confirmed OK; returned destination now Screen. Actual report rendering/archive output still pending.

verified

Posted template invoice report rendered

Path: Accounts receivable > Invoices > All free text invoices > Invoice journal > View > Use print management

FreeTextInvoice.Report rendered successfully through saved Screen destination. Invoice BEAT-000004 dated 2026-10-07, Atlas Demo Customer BEAT-000001, service quantity 1 at 300 USD, tax/charges/discount zero, total 300 USD, Atlas net 30 days and due 2026-11-06. Archive readback and printed credit reference still pending.

failed test

Print archive verification gap

Path: Organization administration > Inquiries and reports > Print archive > Update

Observed menu item: SysPrintArchiveAll

After rendering synthetic BEAT-000004 through print management with Save in print archive selected, Print archive remains empty after Update. Screen rendering passed; persisted archive output not verified. No client records visible.

configured

AP invoice output sorting saved

Path: Accounts payable > Setup > Forms > Form sorting parameters

Observed menu item: VendFormLetterSortingParameters

Added Vendor account then Issued to Selected, confirmed OK and reloaded F&O. Reopened sorting form confirms both keys persisted in that order. Multi-invoice print ordering still requires an output test.

configured

Free-text invoice sorting saved

Path: Accounts receivable > Setup > Forms > Form sorting

Observed menu item: SalesFormLetterSortingParameters

Accounts receivable > Setup > Forms > Form sorting: Free text invoice tab saved and refreshed with Customer account then Invoice. Test3 synthetic BEAT, 2026-10-07, application 10.0.47. Other document tabs and multi-invoice output sorting remain unexecuted.

configured

Customer write-off mapping saved

Path: Accounts receivable > Setup > Customer write-off reason codes

Observed menu item: CustWriteOffFinancialReasonsSetup

Accounts receivable > Setup > Customer write-off reason codes: company beat, existing synthetic BEAT-CRED reason, write-off account 610100, Default No saved and refreshed. No write-off transaction has been executed. Test3 synthetic BEAT, 2026-10-07, application 10.0.47.

configured

Vendor write-off mapping saved

Path: Accounts payable > Setup > Vendor write-off reason codes

Observed menu item: VendWriteOffFinancialReasonsSetup

Accounts payable > Setup > Vendor write-off reason codes: company beat, existing synthetic BEAT-CRED reason, write-off account 610100, Default No saved and refreshed. No vendor write-off transaction executed. Test3 synthetic BEAT, 2026-10-07, application 10.0.47.

validated

BEAT-CASH vendor journal validation passed

Path: Accounts payable > Payments > Vendor payment journal > Lines

Observed menu item: LedgerJournalTable5

AP batch BEAT-000003 / BEAT-AP: vendor BEAT-000001 debit 10 and credit 10 USD, separate vouchers BEAT-140000002/3, BEAT-CASH, Ledger offset 110100, status None. Operation completed and Journal is OK; journal debits/credits 20 each, net zero. Posting is captured separately.

posted

BEAT-CASH vendor paired test posted

Path: Accounts payable > Payments > Vendor payment journal > Lines

Observed menu item: LedgerJournalTable5

AP batch BEAT-000003: Operation completed, Number of vouchers posted to the journal: 2. Paired opposite 10 USD entries BEAT-140000002/3 use vendor BEAT-000001, BEAT-CASH and Ledger offset 110100. No bank file or external payment; settlement and GL readback are separate checks.

verified

BEAT-CASH vendor debit GL verified

Path: Vendor payment journal > Lines > Voucher

Current 2026-10-07 GL BEAT-000007 / BEAT-140000002: vendor balance 210100 +10 USD, Ledger clearing 110100 -10 USD. Paired opposite voucher readback and settlement are separate checks.

verified

BEAT-CASH opposite vendor GL verified

Path: Vendor payment journal > Lines > Voucher

Current 2026-10-07 GL BEAT-000008 / BEAT-140000003: vendor balance 210100 -10 USD, Ledger clearing 110100 +10 USD. Cancels the BEAT-000007 / BEAT-140000002 test voucher exactly. Settlement is a separate check.

verified

BEAT-CASH vendor test fully settled

Path: Accounts payable > Vendors > All vendors > Transactions > Settlement > Settle transactions

Observed menu item: VendTrans

BEAT-140000002 and BEAT-140000003: paired 10 USD vendor entries fully settled; remaining transaction/accounting balances 0.00, Last settlement and Closed date 2026-10-07. Existing BEAT-INV-001 and its original payment remain fully settled.

validated

BEAT-CASH customer journal validation passed

Path: Accounts receivable > Payments > Customer payment journal > Lines

Observed menu item: LedgerJournalTable_CustPaym

AR batch BEAT-000004 / BEAT-AR: customer BEAT-000001 credit 10 and debit 10 USD, separate vouchers BEAT-140000004/5, BEAT-CASH, Ledger offset 110100, None status, no deposit slip. Operation completed and Journal is OK; journal debit/credit totals 20 each, net zero. Posting is a separate check.

posted

BEAT-CASH customer pair posted

Path: Accounts receivable > Payments > Customer payment journal > Lines

Observed menu item: LedgerJournalTable_CustPaym

AR batch BEAT-000004 / BEAT-AR: Operation completed, Number of vouchers posted to the journal: 2. Opposite 10 USD BEAT-140000004/5 use BEAT-000001, BEAT-CASH and Ledger offset 110100. No bank file, external payment or deposit slip. GL and settlement checked separately.

verified

BEAT-CASH customer receipt GL verified

Path: Customer payment journal > Lines > Voucher

Current 2026-10-07 GL BEAT-000009 / BEAT-140000004: customer balance 120100 -10 USD, Ledger clearing 110100 +10 USD. Opposite voucher and settlement checked separately.

verified

BEAT-CASH opposite customer GL verified

Path: Customer payment journal > Lines > Voucher

Current 2026-10-07 GL BEAT-000010 / BEAT-140000005: customer balance 120100 +10 USD, Ledger clearing 110100 -10 USD. Exactly cancels GL BEAT-000009 / BEAT-140000004. Settlement checked separately.

verified

BEAT-CASH customer test fully settled

Path: Accounts receivable > Customers > All customers > Transactions > Settlement > Settle transactions

Observed menu item: CustTrans

BEAT-140000004 and BEAT-140000005: opposite 10 USD customer entries fully settled; remaining transaction/accounting balances 0.00, Last settlement and Closed date 2026-10-07. Synthetic ledger-clearing method test; bank and file integration variants unexecuted.

verified

BEAT-CASH method tests trial balance reconciled

Path: General ledger > Inquiries and reports > Trial balance

Observed menu item: LedgerTrialBalanceListPage

Main account set, Current layer, 2026-01-01 through 2026-12-31: Operation completed; debits and credits 7,640 USD each, net zero. Closing clearing -400, AR/AP/accruals/expense 0, inventory 600, revenue -600, COGS 400 USD. Paired BEAT-CASH tests changed turnover only, not closing balances.

configured

Synthetic BEAT delivery term saved

Path: Accounts payable > Setup > Terms of delivery

Observed menu item: VendDeliveryTerms

Accounts payable > Setup > Terms of delivery: BEAT / Atlas synthetic delivery saved and refreshed. Sales tax address retains User defined; Intrastat code blank. Transportation settings, order assignment and document behavior not tested. Test3 BEAT 2026-10-07, application 10.0.47.

configured

Purchase-order demo form note saved

Path: Accounts payable > Setup > Forms > Form notes

Observed menu item: VendFormLetterRemarks

Accounts payable > Setup > Forms > Form notes: Purchase order / en-US, text BEAT synthetic demonstration only. No commercial commitment. Saved and refreshed after committing actual Form dropdown selection. Printed purchase-order output not tested. Test3 synthetic BEAT, 2026-10-07, application 10.0.47.

configured

Set up Charges code — BEAT

Path: Accounts payable > Charges setup > Charges code

Observed menu item: MarkupTable_Vend

Accounts payable > Charges setup > Charges code: BEAT-FRT / Atlas synthetic freight saved and refreshed in BEAT. Debit Ledger account 610100, posting Purchase, charge; credit Customer/Vendor; Compare purchase order and invoice values Yes. No charge transaction has been posted; matching and tax behavior remain untested.

configured

Set up Vendor charges group — BEAT

Path: Accounts payable > Charges setup > Vendor charges group

Observed menu item: MarkupGroup_Vend

Accounts payable > Charges setup > Vendor charges group: BEAT / Atlas synthetic vendor charges saved and refreshed. The group has not been assigned to a vendor or used in an automatic charge transaction.

configured

Set up Item charges group — BEAT

Path: Accounts payable > Charges setup > Item charges group

Observed menu item: MarkupGroup_Invent

Item charge groups (MarkupGroup_Invent): BEAT / Atlas synthetic item charges saved and refreshed in BEAT. Direct catalog-menu navigation confirmed the form and company; the catalog navigation hierarchy has not yet been independently verified. No product assignment or automatic charge transaction tested. Live module navigation subsequently confirms Accounts payable > Charges setup > Item charge groups; the catalog label Item charges group differs from the observed label.

configured

Set up Line of business — BEAT

Path: Accounts payable > Setup > Line of business

Observed menu item: LineOfBusiness

Accounts payable > Setup > Line of business: BEAT / Atlas synthetic services saved and refreshed. Master classification exists; vendor/customer assignment and reporting behavior remain untested.

configured

Set up Vendor price tolerance groups — BEAT

Path: Accounts payable > Vendors > Vendor price tolerance groups

Observed menu item: VendPriceToleranceGroup

Accounts payable > Vendors > Vendor price tolerance groups: BEAT / Atlas synthetic vendor tolerance saved and refreshed. Group existence only; assignment, tolerance values and invoice matching tests remain unexecuted.

configured

Set up Item price tolerance groups — BEAT

Path: Accounts payable > Invoice matching setup > Item price tolerance groups

Observed menu item: InventItemPriceToleranceGroup

Accounts payable > Invoice matching setup > Item price tolerance groups: BEAT / Atlas synthetic item tolerance saved and refreshed. Master group exists; product assignment and matching tolerance tests remain unexecuted.

configured

Set up Vendor exception groups — BEAT

Path: Accounts payable > Vendors > Vendor exception groups

Observed menu item: VendExceptionGroup

Accounts payable > Vendors > Vendor exception groups: BEAT / Atlas synthetic vendor exception saved and refreshed. Vendor assignment and exception-driven workflow behavior remain untested.

configured

Define price tolerances by item, vendor or combination — BEAT

Path: Accounts payable > Invoice matching setup > Price tolerances

Observed menu item: PurchPriceTolerance

Accounts payable > Invoice matching setup > Price tolerances: saved and refreshed Table item BEAT-ITEM-001 / Table vendor BEAT-000001 / Unit price tolerance percentage 2.00. Existing All/All 0.00 retained. Specific tolerance setup is verified visually; under/over-tolerance invoice tests remain unexecuted.

configured

Set up Matching policy — BEAT

Path: Accounts payable > Invoice matching setup > Matching policy

Observed menu item: PurchLineMatchingPolicy

Accounts payable > Invoice matching setup > Matching policy: item BEAT-ITEM-001 / vendor BEAT-000001 saved and reopened with Three-way matching. Company Three-way matching, override Higher than company policy, level Item and vendor. Earlier core receipt-negative test covered company three-way matching; this newly scoped row has not yet been independently transaction-tested.

configured

Set up Differential reasons — BEAT

Path: Accounts payable > Broker and royalties > Differential reasons

Observed menu item: MCRBrokerDifferentialReason

Accounts payable > Broker and royalties > Differential reasons: BEAT-DIFF / Atlas synthetic broker differential / Main account 610100 saved and refreshed. Broker claim differential posting remains unexecuted.

observed incomplete

Set up Broker contracts — BEAT

Path: Accounts payable > Broker and royalties > Broker contracts

Observed menu item: MCRBrokerContractTable

Accounts payable > Broker and royalties > Broker contracts: BEAT-BROKER synthetic Planning header saved/refreshed, vendor BEAT-000001, dates 2026-10-07 through 2026-12-31, USD, zero charges. No lines or claims; not complete functional broker setup. Vendor charge BEAT-FRT was rejected by broker charge lookup and removed before save; customer-side charge dependency still requires review. No commercial agreement or payment created.

configured

Set up Royalty agreements — BEAT

Path: Accounts payable > Broker and royalties > Royalty agreements

Observed menu item: MCRRoyaltyTable

Accounts payable > Broker and royalties > Royalty agreements: BEAT-ROYALTY / line BEAT-ROY synthetic unvalidated draft saved/refreshed, vendor BEAT-000001, dates 2026-10-07 to 2026-12-31, ea/USD, accrual 220100, expense 610100. Selection saved item BEAT-ITEM-001, ea, site/warehouse BEAT. Validated remains No; no claim generation, approval or posting tested.

configured

royalty rate range — BEAT

Path: Direct form inspection: MCRRoyaltyTable

Observed menu item: MCRRoyaltyTable

Saved BEAT-ROYALTY line pricing range From 0.00 / To 100.00 / Value 1.0000 USD per ea. Cumulate Invoice, Gross, Quantity. Refreshed saved setup only; Validated No and royalty calculation/posting untested.

configured

Set up Charges code — BEAT

Path: Accounts receivable > Charges setup > Charges code

Observed menu item: MarkupTable_Cust

Live path Accounts receivable > Charges setup > Charges code (catalog includes Setup): BEAT-FRT / Atlas synthetic freight revenue saved/refreshed, debit Customer/Vendor, credit Ledger 410100 / Sales order revenue, Prorate No. No sales charge posting or tax test yet. Catalog hierarchy drift is recorded here; catalog menu path remains provenance until separately reviewed.

configured

Set up Customer charge group — BEAT

Path: Accounts receivable > Charges setup > Customer charge groups

Observed menu item: MarkupGroup_Cust

Live path Accounts receivable > Charges setup > Customer charge groups: BEAT saved/refreshed, stored description Atlas synthetic customer charg (field truncation). Catalog hierarchy includes Setup and singular Customer charge group. Group not assigned to customer or transaction-tested.

configured

Set up Delivery charges groups — BEAT

Path: Accounts receivable > Charges setup > Delivery charges groups

Observed menu item: MarkupGroup_Delivery

Live path Accounts receivable > Charges setup > Delivery charges groups: BEAT / Atlas demo delivery charges saved/refreshed. Catalog hierarchy includes Setup; live menu shows Charges setup directly under Accounts receivable. Delivery assignment/charge application untested.

configured

Set up Auto charges — BEAT

Path: Accounts receivable > Charges setup > Auto charges

Observed menu item: MarkupAutoSetup_Cust

Live path Accounts receivable > Charges setup > Auto charges: Header/Table customer BEAT-000001, All items/delivery modes, description BEAT synthetic 5 USD freight, one USD BEAT-FRT Fixed 5.00 line, Keep No; saved/refreshed and unused blank line removed. Catalog hierarchy includes Setup. Future synthetic customer orders may receive the charge; application and posting remain untested.

configured

Set up Invoice origin codes — BEAT

Path: Accounts receivable > Setup > Invoice origin codes

Observed menu item: CustomerInvoiceOrigin

Accounts receivable > Setup > Invoice origin codes: BEAT / Atlas synthetic invoice origin saved/refreshed. Origin type assignment unchecked and origin type disabled/blank; no automatic origin assignment or invoice usage tested.

configured

Set up Trading partner codes — BEAT

Path: Accounts receivable > Setup > Trading partner codes

Observed menu item: CustTradingPartnerCode

Accounts receivable > Setup > Trading partner codes: BEAT / Atlas synthetic trading partner saved/refreshed. No external trading partner connection, customer assignment or electronic document transmission tested.

configured

Set up Sales agreement classifications — BEAT

Path: Accounts receivable > Setup > Sales agreement classifications

Observed menu item: SalesAgreementClassification

Accounts receivable > Setup > Sales agreement classifications: BEAT / Atlas synthetic sales agreement saved/refreshed, category Default, line matching Company policy. Agreement creation/release orders and fulfillment tests remain unexecuted.

observed incomplete

Set up Electronic document property types — BEAT

Path: Accounts receivable > Setup > Electronic document property types

Observed menu item: EInvoicePropertyTypeTable

Accounts receivable > Setup > Electronic document property types: custom BEAT-DEMO / BEAT synthetic / Atlas demo property saved/refreshed, Sorting 0. Applicable to remains blank. Applicability lookup returned no choices and a multiple-form lookup message; no applicability mapping or e-invoice configuration/transmission verified. Saved type alone is incomplete functional setup.

configuration gap

Set up Electronic signature certificates — BEAT

Path: Accounts receivable > Setup > Electronic signature certificates observed in BEAT

Observed menu item: XmlCertificate

Accounts receivable > Setup > Electronic signature certificates observed in BEAT: no active populated certificate, issuer, subject or validity dates. Requires an appropriate certificate/Key Vault configuration and signing scope from the owner; none supplied. No certificate generated/imported or signing activated. This is dependency evidence, not positive configured setup.

configured

Set up Billing classifications — BEAT

Path: Accounts receivable > Setup > Billing classifications

Observed menu item: CustBillingClassification

Accounts receivable > Setup > Billing classifications: BEAT / Atlas synthetic billing, Priority 1, NET30, restriction No saved/refreshed. Interest/collection overrides and classification-specific invoice/credit sequences blank; billing code assignment and public-sector billing transactions still pending.

configured

Set up Billing code custom fields — BEAT

Path: Accounts receivable > Setup > Billing code custom fields

Observed menu item: CustCustomField

Accounts receivable > Setup > Billing code custom fields: BEAT-REF saved/refreshed, Type Text, default BEAT synthetic only, Maximum length 255. Billing code linking and invoice field propagation remain untested.

configured

Set up Billing codes — BEAT

Path: Accounts receivable > Setup > Billing codes

Observed menu item: CustBillingCode

Accounts receivable > Setup > Billing codes: BEAT-SVC / Atlas synthetic service billing saved/refreshed, Effective 2026-10-07 / Never, USD Line amount 300.00, 100% ledger 410100, Allow account/amount changes Yes, BEAT-REF Text Active Yes / Required No. Code/classification association and billing invoice execution remain pending; no external billing.

configured

Set up Customers advanced notes groups — BEAT

Path: Accounts receivable > Setup > Advanced notes > Customers advanced notes groups

Observed menu item: CustNotesGroup_IT

Accounts receivable > Setup > Advanced notes > Customers advanced notes groups: BEAT-AR / Atlas synthetic customer notes / Module Customer saved/refreshed in USA BEAT. Availability of this IT menu does not verify Italian localization or printed-output behavior; assignment/output untested.

configured

Set up Customers advanced notes setup — BEAT

Path: Accounts receivable > Setup > Advanced notes > Customers advanced notes setup

Observed menu item: CustFreeNotes_IT

Accounts receivable > Setup > Advanced notes > Customers advanced notes setup: Header/Table BEAT-000001, Invoice Yes, Free text invoice Yes, External restriction; note BEAT synthetic demonstration only. No commercial commitment. saved/refreshed. Other document flags No. USA screenshot verifies saved values only; printed note/localization behavior untested.

configured

Set up Period charge rule — BEAT

Path: Accounts receivable > Charges setup > Period charge rule

Observed menu item: MarkupPeriodChargeRule

Accounts receivable > Charges setup > Period charge rule: BEAT-PERIOD synthetic rule saved/refreshed, Table customer BEAT-000001, site/warehouse BEAT, dates 2026-10-07 through 2026-12-31. Monetary threshold line 100.00 USD, charge BEAT-FRT, revenue 410100, debit-only No. Period charge calculation/invoicing unexecuted; other disabled quantity/charge-amount fields retain zero/blank.

configured

Set up Payment calendar — BEAT

Path: Payment calendar (PaymCalendar), opened from Accounts receivable > Payments setup > Payment calendar

Observed menu item: PaymCalendar

Payment calendar (PaymCalendar), opened from Accounts receivable > Payments setup > Payment calendar; the same form is listed under Accounts payable > Payment setup. BEAT-WEEK / Atlas synthetic Monday-Friday saved/refreshed, Monday-Friday business Yes, Saturday/Sunday No, Location calendar No, no holiday exceptions. Calendar master only; due-date adjustment tests remain unexecuted.

configured

Set up Payment calendar configuration — BEAT

Path: Accounts receivable > Payments setup > Payment calendar configuration

Observed menu item: PaymCalendarRuleCustomer

Accounts receivable > Payments setup > Payment calendar configuration: Specific rule BEAT-AR / Synthetic cash method calendar saved/refreshed, BEAT-WEEK calendar, Method Code BEAT-CASH, Terms All, Active Yes. Prioritization/selection and due-date adjustment transaction behavior remain untested.

configured

Customer payment fee

Path: Accounts receivable > Payments setup > Payment fee > Payment fee setup. Saved BEAT-FEE synthetic fee with Customer charge and Daily journal

Observed menu item: CustPaymFee

Accounts receivable > Payments setup > Payment fee > Payment fee setup. Saved BEAT-FEE synthetic fee with Customer charge and Daily journal; rule All banks, BEAT-CASH, USD, Amount 1 USD. No bank information supplied. Fee application and posting remain untested.

configuration gap

Netting automation dependencies

Path: Accounts receivable > Payments > Netting > Process automations

Observed menu item: CustVendNettingAutomationScheduleSeries

Historical prerequisite observation: Automatic netting schedule type is available for beat. The missing eligible journal/agreement was subsequently resolved by saved BEAT-NET journal and activated scoped agreement/rule. Series execution remains pending. The earlier batch warning names the deleted-reference retention scan, not the process-automation framework; no process-automation outage is established by that warning.

configuration gap

Netting agreement journal prerequisite (resolved journal prerequisite)

Path: Observed shared netting form through Accounts receivable > Payments > Netting > Netting agreements. BEAT-NET draft attempted with synthetic description, Inactive status and clearing account 110100. Journal name lookup had no eligible rows

Observed menu item: CustVendNettingAgreement

Observed shared netting form through Accounts receivable > Payments > Netting > Netting agreements. BEAT-NET draft attempted with synthetic description, Inactive status and clearing account 110100. Journal name lookup had no eligible rows; save/add-line blocked: Journal name must be filled in. Draft not treated as saved or active. Eligible netting journal and party mapping are prerequisites; no netting posted.

observed incomplete

Inactive netting rule (superseded by active scoped rule)

Path: Shared Netting rules form opened through Accounts receivable > Payments > Netting. Saved BEAT-NET, Inactive synthetic netting rule, Active No, selected agreements, newest-to-oldest due-date order, credit/debit notes No. No agreement or criteria associated

Observed menu item: CustVendNettingRule

Shared Netting rules form opened through Accounts receivable > Payments > Netting. Saved BEAT-NET, Inactive synthetic netting rule, Active No, selected agreements, newest-to-oldest due-date order, credit/debit notes No. No agreement or criteria associated; eligible netting journal/party setup remains a prerequisite. No activation or netting execution claimed.

configuration gap

Catalog payment-gateway access limitation

Path: Direct form inspection: CreditCardRequestWithIssue

Observed menu item: CreditCardRequestWithIssue

Focused catalog menu-item verification in BEAT returned Access Denied for CreditCardRequestWithIssue. Live AR Payments setup exposes Payment services (CreditCardProcessors), a different page, with no default processor and a warning that a credit card cannot be created. No provider credentials, card data, connector activation or access expansion performed. Catalog lifecycle path/form remains unverified; owner-approved sandbox provider and correct menu/access are prerequisites.

configured

Vendor advanced notes group

Path: Accounts payable > Setup > Advanced notes > Vendors advanced notes groups. Saved/refreshed BEAT-AP, Atlas synthetic vendor notes, Vendor module. USA BEAT exposes this form

Observed menu item: VendNotesGroup_IT

Accounts payable > Setup > Advanced notes > Vendors advanced notes groups. Saved/refreshed BEAT-AP, Atlas synthetic vendor notes, Vendor module. USA BEAT exposes this form; localization applicability and group assignment/printed output remain untested.

configured

Vendor advanced note

Path: Accounts payable > Setup > Advanced notes > Vendors advanced notes setup. Header Table BEAT-000001, Purchase order Yes, External restriction, saved/refreshed text BEAT synthetic demonstration only. No commercial commitment. Group exists separately

Observed menu item: VendFreeNotes_IT

Accounts payable > Setup > Advanced notes > Vendors advanced notes setup. Header Table BEAT-000001, Purchase order Yes, External restriction, saved/refreshed text BEAT synthetic demonstration only. No commercial commitment. Group exists separately; this note uses vendor Table scope. Printed output and localization applicability remain untested.

configuration gap

Invoice issue date interval prerequisite

Path: Accounts payable > Setup > Set up calculation for invoice issue due date. Visible Domestic/start 10/7/2026 row has blank Date interval code, with empty Date intervals lookup. No rule saved. Date interval definition, intended jurisdiction and invoice issue-date scenario must be established before configuration

Observed menu item: LedgerInvoiceIssueDueDateSetup_W

Accounts payable > Setup > Set up calculation for invoice issue due date. Visible Domestic/start 10/7/2026 row has blank Date interval code, with empty Date intervals lookup. No rule saved. Date interval definition, intended jurisdiction and invoice issue-date scenario must be established before configuration; NET30 payment due dates are a separate tested setup.

configured

Purchase summary update parameters

Path: Accounts payable > Setup > Summary update parameters. Saved/refreshed Default values for summary update None, Order error tolerance Error. BEAT keeps individual-order processing and strict batch error handling. Receipts/product receipt/invoice grouping fields and multi-order summary tests remain unverified.

Observed menu item: PurchSummaryParameters

Accounts payable > Setup > Summary update parameters. Saved/refreshed Default values for summary update None, Order error tolerance Error. BEAT keeps individual-order processing and strict batch error handling. Receipts/product receipt/invoice grouping fields and multi-order summary tests remain unverified.

configured

Vendor automatic freight charge

Path: Accounts payable > Charges setup > Automatic charges. Header Table vendor BEAT-000001, All items/delivery, description BEAT synthetic 5 USD freight. One saved/refreshed USD BEAT-FRT Fixed 5.00 line, Compare purchase order and invoice values Yes. Future test orders may receive this charge

Observed menu item: MarkupAutoSetup_Vend

Accounts payable > Charges setup > Automatic charges. Header Table vendor BEAT-000001, All items/delivery, description BEAT synthetic 5 USD freight. One saved/refreshed USD BEAT-FRT Fixed 5.00 line, Compare purchase order and invoice values Yes. Future test orders may receive this charge; allocation/application, tax and invoice matching tests remain unexecuted.

configured

Vendor invoice template

Path: Accounts payable > Invoices > Recurring invoices > Vendor invoice templates. Saved/refreshed BEAT-SVC, Atlas synthetic vendor service, BEAT posting profile, USD NET30 BEAT-CASH. One BEAT-ITEM-001 ea line, quantity 1, unit price/amount 100 USD. Assigned Vendors inquiry empty

Observed menu item: VendInvoiceTemplate

Accounts payable > Invoices > Recurring invoices > Vendor invoice templates. Saved/refreshed BEAT-SVC, Atlas synthetic vendor service, BEAT posting profile, USD NET30 BEAT-CASH. One BEAT-ITEM-001 ea line, quantity 1, unit price/amount 100 USD. Assigned Vendors inquiry empty; vendor assignment, generation schedule, distributions and generated invoice posting remain untested.

configured

Payment report cover page

Path: Accounts payable > Payment setup > Cover page for payments report. Saved/refreshed report title BEAT synthetic payments — demonstration only, Landscape, one signature line, print date/company name Yes, logo No. No personal signatory entered. Print test/output remains unexecuted

Observed menu item: VendCoverPageSetup

Accounts payable > Payment setup > Cover page for payments report. Saved/refreshed report title BEAT synthetic payments — demonstration only, Landscape, one signature line, print date/company name Yes, logo No. No personal signatory entered. Print test/output remains unexecuted; this is report layout, not payment approval.

configured

Vendor payment calendar rule

Path: Accounts payable > Payment setup > Payment calendar configuration. Saved/refreshed Specific BEAT-AP rule, BEAT-WEEK Monday-Friday calendar, Method Code BEAT-CASH, Terms All, Active Yes. Prioritize rules, Select calendars and resulting document due-date adjustment remain untested.

Observed menu item: PaymCalendarRuleVendor

Accounts payable > Payment setup > Payment calendar configuration. Saved/refreshed Specific BEAT-AP rule, BEAT-WEEK Monday-Friday calendar, Method Code BEAT-CASH, Terms All, Active Yes. Prioritize rules, Select calendars and resulting document due-date adjustment remain untested.

configured

Synthetic payment format code set

Path: Accounts payable > Payment setup > Payment format code sets. Saved/refreshed Service level BEAT, description Synthetic only - not bank approved. Unassigned demo lookup value

Observed menu item: PaymentFormatCodeSets_W

Accounts payable > Payment setup > Payment format code sets. Saved/refreshed Service level BEAT, description Synthetic only - not bank approved. Unassigned demo lookup value; no ISO/bank-approved meaning claimed, no export format assignment or bank file generation/transmission. Bank specification is required for functional format configuration.

configured

Synthetic return error code

Path: Accounts payable > Payment setup > Return format error codes. Saved/refreshed BEAT-ERR, Synthetic rejected payment example, Name BEAT demo only. Demonstration lookup entry only

Observed menu item: BankReturnFormatErrorCodes_W

Accounts payable > Payment setup > Return format error codes. Saved/refreshed BEAT-ERR, Synthetic rejected payment example, Name BEAT demo only. Demonstration lookup entry only; no bank error specification, return format assignment, sample-file import or payment reconciliation tested.

configured

Synthetic return status mapping

Path: Accounts payable > Payment setup > Return format status mapping. Saved/refreshed return status BEAT-REJEC (ten-character field truncation), Payment status Rejected, BEAT synthetic rejected example. Demonstration only, no bank meaning claimed. No bank return file import/status update/reconciliation tested.

Observed menu item: VendPaymReconciliationReturnStatus_W

Accounts payable > Payment setup > Return format status mapping. Saved/refreshed return status BEAT-REJEC (ten-character field truncation), Payment status Rejected, BEAT synthetic rejected example. Demonstration only, no bank meaning claimed. No bank return file import/status update/reconciliation tested.

configured

Vendor payment fee

Path: Accounts payable > Payment setup > Payment fee > Payment fee setup. BEAT-FEE, synthetic vendor payment fee, Vendor charge/Daily journal. Saved/refreshed All bank relations, BEAT-CASH, USD, Amount 1 USD. No banking data supplied. Fee application and resulting vendor/ledger posting remain untested.

Observed menu item: VendPaymFee

Accounts payable > Payment setup > Payment fee > Payment fee setup. BEAT-FEE, synthetic vendor payment fee, Vendor charge/Daily journal. Saved/refreshed All bank relations, BEAT-CASH, USD, Amount 1 USD. No banking data supplied. Fee application and resulting vendor/ledger posting remain untested.

configured

Disabled vendor payment proposal automation

Path: Accounts payable > Payment setup > Process automations. Saved BEAT-AP-PROPOSAL Vendor payment proposal, BEAT company, Daily 23:00 UTC 10/8-10/9/2026, BEAT-AP journal, USD amount limit 10, Ledger 110100, check vendor balance Yes, other companies No. Immediately disabled series

Observed menu item: VendPaymProcessScheduleSeries

Accounts payable > Payment setup > Process automations. Saved BEAT-AP-PROPOSAL Vendor payment proposal, BEAT company, Daily 23:00 UTC 10/8-10/9/2026, BEAT-AP journal, USD amount limit 10, Ledger 110100, check vendor balance Yes, other companies No. Immediately disabled series; live grid Enabled No and both occurrences DISABLED. No occurrence run, proposal generated or payment posted. Earlier batch warning remains an execution readiness concern.

configured

Vendor invoice policy rule type

Path: Accounts payable > Setup > Policy setup > Vendor invoice policy rule types. Saved/refreshed BEAT-INVOICE with Atlas synthetic invoice policy description, AOT query VendInvoicePolicyHeader (live title Vendor invoice), Document type Vendor invoices. Rule type alone does not enforce policy

Observed menu item: VendInvoicePolicyRuleType

Accounts payable > Setup > Policy setup > Vendor invoice policy rule types. Saved/refreshed BEAT-INVOICE with Atlas synthetic invoice policy description, AOT query VendInvoicePolicyHeader (live title Vendor invoice), Document type Vendor invoices. Rule type alone does not enforce policy; policy rule conditions, organization assignment and positive/negative invoice tests remain unexecuted.

configuration gap

Invoice policy precedence and organization prerequisites

Path: Accounts payable > Setup > Policy setup > Vendor invoice policies. Saved BEAT-DEMO synthetic policy shell, explicitly unassigned/non-enforcing. Live form reports Order of precedence is not set

Observed menu item: Action:VendInvoicePolicies

Accounts payable > Setup > Policy setup > Vendor invoice policies. Saved BEAT-DEMO synthetic policy shell, explicitly unassigned/non-enforcing. Live form reports Order of precedence is not set; hierarchy/available/selected organizations empty, BEAT-INVOICE(0) has no policy rules. Company policy precedence/organization scope and concrete rule conditions must be defined before enforcement. No policy control test or security change claimed.

configuration gap

Invoice expenditure reviewer prerequisites

Path: Accounts payable > Setup > Policy setup > Vendor invoice expenditure reviewers. Empty participant/legal entity definitions

Observed menu item: VendInvoiceWorkflowParticipantExpenToken

Accounts payable > Setup > Policy setup > Vendor invoice expenditure reviewers. Empty participant/legal entity definitions; Organization distributions reports Account structures that include financial dimensions have not been selected for the ledger. Current BEAT uses main-account-only structure. Intended organizational dimensions and reviewer/workflow owners must be established; no approval authority or security access granted.

configuration gap

Invoice capture integration prerequisites

Path: Accounts payable > Setup > Invoice capture. Live Enable parameters for invoice capture form exposes no named synced legal entity, no attachment document type/journal mapping

Observed menu item: InvoiceCapture

Accounts payable > Setup > Invoice capture. Live Enable parameters for invoice capture form exposes no named synced legal entity, no attachment document type/journal mapping; visible blank row defaults Sync all vendors Yes and Transfer attachment Yes. No values saved, sync enabled or data transferred. Requires installed/configured Invoice Capture Dataverse environment, approved connection and explicit BEAT-only mapping before testing synthetic document ingestion.

configuration gap

Payment plan template catalog access gap

Path: Catalog path Accounts payable > Payments > Payment plans > Payment plan templates is absent from fully expanded USA BEAT menu. Focused catalog menu PaymentPlanTemplate returned Access Denied. No template created or permissions changed. Correct product/version/feature/localization and menu eligibility must be confirmed

Observed menu item: PaymentPlanTemplate

Catalog path Accounts payable > Payments > Payment plans > Payment plan templates is absent from fully expanded USA BEAT menu. Focused catalog menu PaymentPlanTemplate returned Access Denied. No template created or permissions changed. Correct product/version/feature/localization and menu eligibility must be confirmed; existing payment schedules are a different form.

configuration gap

Payment plan catalog menu missing

Path: Catalog Accounts payable > Payments > Payment plans > Payment plans is absent from expanded BEAT navigation. Focused PaymentPlanOverview verification reports The menu item with name paymentplanoverview does not exist and No object specified on menu item paymentplanoverview. No payment plan created. Catalog product/version mapping requires correction or owner-supplied applicable implementation

Observed menu item: PaymentPlanOverview

Catalog Accounts payable > Payments > Payment plans > Payment plans is absent from expanded BEAT navigation. Focused PaymentPlanOverview verification reports The menu item with name paymentplanoverview does not exist and No object specified on menu item paymentplanoverview. No payment plan created. Catalog product/version mapping requires correction or owner-supplied applicable implementation; not equivalent to payment schedules.

configuration gap

AP revaluation automation catalog access gap

Path: Catalog Accounts payable > Periodic tasks > Foreign currency revaluation automation is not in expanded USA BEAT navigation

Observed menu item: VendExchRateAdjAutomationScheduleSeries

Catalog Accounts payable > Periodic tasks > Foreign currency revaluation automation is not in expanded USA BEAT navigation; ordinary Foreign currency revaluation is available. Focused catalog VendExchRateAdjAutomationScheduleSeries returned Access Denied. No automation or revaluation executed. Version/feature/menu eligibility and foreign-currency open items, exchange rates and unrealized gain/loss accounts must be established. Microsoft Learn describes ordinary AP/AR revaluation with batch scheduling; bank automation is a different scope.

configuration gap

AR revaluation automation catalog access gap

Path: Catalog Accounts receivable > Periodic tasks > Foreign currency revaluation automation is absent from expanded USA BEAT navigation

Observed menu item: CustExchRateAdjAutomationScheduleSeries

Catalog Accounts receivable > Periodic tasks > Foreign currency revaluation automation is absent from expanded USA BEAT navigation; ordinary Foreign currency revaluation is present. Focused catalog CustExchRateAdjAutomationScheduleSeries returned Access Denied. No automation or revaluation executed. Version/feature/menu eligibility, foreign-currency open customer transactions, exchange rates and unrealized gain/loss accounts remain prerequisites. Ordinary batch revaluation is distinct from the catalog automation page.

configuration gap

Customer payment-ID catalog access gap

Path: Catalog Accounts receivable > Setup > Payment setup > Payment ID is absent from expanded USA BEAT navigation. Focused BankCustPaymIdTable verification returned Access Denied. No payment ID definition or security expansion. Intended bank/country reference standard, length/positions/check digits and correct menu eligibility remain required before generation/validation tests.

Observed menu item: BankCustPaymIdTable

Catalog Accounts receivable > Setup > Payment setup > Payment ID is absent from expanded USA BEAT navigation. Focused BankCustPaymIdTable verification returned Access Denied. No payment ID definition or security expansion. Intended bank/country reference standard, length/positions/check digits and correct menu eligibility remain required before generation/validation tests.

configuration gap

Payment file integration catalog path unresolved

Path: Expanded live Accounts payable > Setup menu in USA BEAT has no Payment file integration parameters link. Catalog record supplies no menu item/form name

Expanded live Accounts payable > Setup menu in USA BEAT has no Payment file integration parameters link. Catalog record supplies no menu item/form name; no exact target can be verified. This screenshot proves the inspected menu only, not global feature absence. Correct integration product/form and bank/provider specification are required. BEAT-CASH uses Ledger clearing; no export format, endpoint, credentials or file transmission configured. Microsoft Learn describes payment formats under methods of payment, not this exact catalog parameter page.

observed incomplete

Security configuration: existing AP clerk invoice duty

Path: System administration > Security > Security configuration

Observed menu item: SysSecConfiguration

Read-only inspection: Accounts payable clerk (VendInvoiceAccountsPayableClerk) includes Maintain vendor invoices (VendInvoiceVendorInvoicesMaintain). Unpublished objects remain zero. No role assignment, privilege or security expansion performed. Exact matching privileges, segregation-of-duties and BEAT non-administrator execution remain unverified.

configured

Required netting journal name saved

Path: General ledger > Journal setup > Journal names

Observed menu item: LedgerJournalSetup

BEAT-NET / Atlas synthetic customer vendor netting saved and refreshed with Customer and vendor netting journal type, voucher series Acco_116, Current layer. This resolves the empty eligible journal lookup prerequisite; no netting transaction has been posted yet.

verified setup

BEAT netting agreement activated

Path: Accounts receivable > Payments > Netting > Netting agreements

Observed menu item: CustVendNettingAgreement

BEAT-NET agreement saved and Active. Journal BEAT-NET, bridge Ledger 110100, same-company beat customer BEAT-000001 and vendor BEAT-000001, effective 10/7/2026 to 12/31/2026. Activation succeeded; eligible journal prerequisite resolved. Synthetic paired accounts only; no netting posting yet.

verified setup

Scoped BEAT netting rule Active

Path: Accounts receivable > Payments > Netting > Netting rules

Observed menu item: CustVendNettingRule

BEAT-NET rule now Active Yes, Selected agreements contains only active BEAT-NET, newest-to-oldest due date sequence, credit/debit notes No. No additional criteria required because agreement limits accounts/company. Prior inactive/unassigned observation superseded; actual netting execution pending.

configured

Vendor recurring template assignment saved

Path: Accounts payable > Vendors > All vendors > Invoice > Recurring invoices

Observed menu item: VendTableListPage

BEAT-SVC assigned to synthetic vendor BEAT-000001. Active Yes, template defaults, Daily Per 1, start 10/7/2026, end 10/8/2026, maximum cumulative amount 100 USD; saved and refreshed. F&O confirmed only one invoice for the bounded date range. Same-day start/end failed validation; corrected end date resolves assignment validation. Generation and posting test follows.

verified generation

Vendor recurring invoice generation succeeded

Path: Accounts payable > Invoices > Recurring invoices > Generate vendor recurring invoices

Observed menu item: Action:VendRecurrenceInvoiceServiceOperation

Foreground BEAT-SVC generation on 10/7/2026 returned Recurring invoice BEAT-00001 was created successfully. This verifies assigned template generation, not posting. Action center clarifies the earlier required batch warning concerns Scans for deleted references which have reached the end of their retention period, not the process-automation task; no shared retention batch settings changed.

functionally verified

Recurring vendor invoice posting completed

Path: Accounts payable > Invoices > Recurring invoices > Post pending vendor recurring invoices

Observed menu item: VendInvoiceInfoListPage

Generated recurring invoice BEAT-00001-1 for vendor BEAT-000001, 100 USD, was posted successfully. Finance returned posting-process-complete and Operation completed; pending list became empty. Voucher and ledger reconciliation remain a separate checkpoint.

observed incomplete

Recurring vendor invoice balanced subledger

Path: Accounts payable > Inquiries and reports > Invoice > Invoice journal > View accounting

Observed menu item: VendInvoiceJournal

Invoice BEAT-00001-1, voucher BEAT-110000002, subledger BEAT-000000012: expense 610100 debit 100 USD and vendor balance 210100 credit 100 USD. Transaction/accounting debit and credit totals each 100. Voucher transactions remained empty after refresh, so GL transfer/reconciliation is pending; no complete GL verification claimed.

functionally verified

Recurring vendor invoice general ledger reconciled

Path: Accounts payable > Inquiries and reports > Invoice > Invoice journal > Voucher

Observed menu item: LedgerTransVoucher1

After Transfer now for the single BEAT subledger entry, GL BEAT-000017 / voucher BEAT-110000002 shows payable 210100 -100 USD and expense 610100 +100 USD, Current layer dated 10/7/2026. Invoice BEAT-00001-1 and balanced subledger BEAT-000000012 reconcile to the GL. Settlement remains open for netting verification.

functionally verified

Synthetic receivable posted for netting test

Path: Accounts receivable > Invoices > All free text invoices

Observed menu item: CustFreeInvoiceListPage

BEAT-000006 posted for BEAT-000001 from BEAT-SERVI template, 1 x 100 USD revenue 410100, NET30. Initial attempt canceled with stale duplicate credit voucher BEAT-40000004; session reload then same saved draft posted successfully, Accounting Completed, Posted Yes. Netting settlement and GL readback remain separate checks; numbering root cause remains unconfirmed.

functionally verified

BEAT customer/vendor netting posted

Path: Accounts receivable > Payments > Netting > Customer and vendor balance netting > Create netting

Observed menu item: CustVendNettingOverview

BEAT-NET, posting date 10/7/2026, only customer invoice BEAT-000006 +100 USD and vendor invoice BEAT-00001-1 -100 USD marked. Estimated residuals zero. Finance returned Number of vouchers posted to the journal: 2; both open-invoice grids became empty and displayed customer/vendor balances zero. History and GL reconciliation are separate next checks.

functionally verified

BEAT netting history Posted and both accounts cleared

Path: Accounts receivable > Payments > Netting > Customer and vendor balance netting > Netting history

Observed menu item: CustVendNettingHistory

Journal batch BEAT-000008 / agreement BEAT-NET dated 10/7/2026: Customer BEAT-000001 netting -100 USD, one invoice +100; Vendor BEAT-000001 netting +100 USD, one invoice -100; both Status Posted. Cleared overview explicitly read back customer/vendor open balances 0.00. Manual netting succeeded; active rule and scheduled automation not thereby tested.

functionally verified

BEAT trial balance reconciled after invoice and netting

Path: General ledger > Inquiries and reports > Trial balance

Observed menu item: LedgerTrialBalanceListPage

Refreshed 1/1/2026–12/31/2026, Main account set, Current layer. Debit and credit totals both 8040 USD, net zero. Closing: clearing 110100 -400, AR120100 0, inventory130100 600, receipt/accrual140100/220100 0, AP210100 0, revenue410100 -700, COGS510100 400, expense610100 100. Clearing debit/credit increased 100 each from netting bridge and net unchanged; netting history and invoice subledger/GL readback support reconciliation.

functionally verified

BEAT netting reversal control verified

Path: Accounts receivable > Payments > Netting > Customer and vendor balance netting history > Reverse netting

Observed menu item: CustVendNettingHistory

Reversed only synthetic BEAT-000008 dated 10/7/2026. Action Center reports two vouchers posted; customer and vendor history rows now Status Reversed, contained invoices 0 and total invoice amount 0.00. Reopened balances and rule-based re-netting checked next.

functionally verified

Automatic netting rule produced correct preview

Path: Accounts receivable > Payments > Netting > Customer and vendor balance netting > Automatic netting

Observed menu item: CustVendNettingOverview

Selected BEAT-NET active rule, posting 10/7/2026, invoice due date 11/6/2026, Preview before posting Yes. Preview contains only BEAT-NET pair BEAT-000001 customer/vendor, USD100 each, one invoice per side. This verifies rule selection after reversal reopened +100/-100; posting result and recurring series are separate checks.

functionally verified

Scoped automatic netting rule posted successfully

Path: Accounts receivable > Payments > Netting > Customer and vendor balance netting > Automatic netting > Preview > Post

Observed menu item: CustVendNettingOverview

BEAT-NET rule preview posted: Action Center Number of vouchers posted to the journal: 2. Refreshed Not cleared overview empty, confirming +100/-100 pair no longer open. Foreground rule-driven netting verified; scheduled process-automation series remains untested.

functionally verified

Final BEAT ledger after reversal and rule re-netting

Path: General ledger > Inquiries and reports > Trial balance

Observed menu item: LedgerTrialBalanceListPage

Recalculated full-year 2026/Main account set/Current after reversal and rule-driven re-netting: debit/credit 8040 USD each, net zero. Closing clearing -400, inventory600, revenue-700, COGS400, expense100; AR/AP and receipt/purchase accruals zero. Netting controls restored the same balanced final ledger state.

configuration gap

Invoice deadline availability prerequisite not found in feature list

Path: System administration > Workspaces > Feature management > All

Observed menu item: FeatureManagementWorkspace

In Test3 Finance 10.0.47, All feature names filtered Invoice issue deadline then *deadline* returned no rows. Microsoft Learn describes Invoice issue deadline availability as a global feature, so USA BEAT alone is not grounds to declare this scenario inapplicable. Feature/list/menu availability remains unresolved; no shared feature flags changed and no deadline control validated.

Remaining verification

• 14 configuration prerequisite/access/catalog gaps require resolution; see the completion audit.
• Four incomplete observations need downstream setup or security testing.
• Saved optional configuration requires bounded transaction/output tests.
• Original-invoice reference duplicate-voucher and print archive failures remain unresolved.
• Human Editorial Desk review and preview approval required before publication.
• Invoice capture: Explicitly deferred by user; identify Dataverse environment later.
• Netting: Manual netting, reversal and foreground BEAT-NET rule preview/posting verified; final full-year Current trial balance 8040 USD debit/credit and net zero, AR/AP zero. Recurring process-automation series remains untested.
• Recurring vendor invoice: BEAT-SVC assignment, generation, posting and GL reconciliation verified for invoice BEAT-00001-1 / voucher BEAT-110000002 / GL BEAT-000017, 100 USD.

Microsoft: Configure ledgers