Books Examination Findings and Product Questions
Findings
| id | severity | statement | affects | evidence | kind |
|---|---|---|---|---|---|
FND-ACC-BKS-001 | medium | Books configuration is hosted by the shared Configuration surface and its Accounting resources. The corrected registry scope replaces the draft brief’s Accounting page-group assumption. | MOD-ACC-BKS | Structured evidence | inconsistency |
FND-ACC-BKS-002 | low | The configuration catalogue marks 53 journeys not started and one blocked despite 28 existing browser specifications. Bindings use the specifications rather than treating catalogue automation flags as evidence of absence. | JNY-ACC-BKS-001, JNY-ACC-BKS-002, JNY-ACC-BKS-003, JNY-ACC-BKS-004, JNY-ACC-BKS-005, JNY-ACC-BKS-006 | Structured evidence | inconsistency |
FND-ACC-BKS-003 | medium | Twenty-six catalogue variants lack browser specifications: 0005, 0012, 0015–0017, 0024, 0028–0029, 0031–0032, 0034–0039, 0042–0045 and 0049–0054. The approved coverage deviation still requires P1 delivery before the next milestone verification. | CAP-ACC-BKS-007, CAP-ACC-BKS-008, CAP-ACC-BKS-012, CAP-ACC-BKS-016, JNY-ACC-BKS-006 | Structured evidence | debt |
FND-ACC-BKS-004 | medium | The earlier acceptance inventory misstates accounting-method mutability and invoice-used term deletion handling. Current rules use pinned implementation instead of those stale claims. | CAP-ACC-BKS-003, CAP-ACC-BKS-011, BR-CAP-ACC-BKS-003-01 | Structured evidence | inconsistency |
FND-ACC-BKS-005 | low | The API description gives conflicting accounting-method guards. Implementation uses posted or downloaded work in the current open period, consistent with the recorded repair decision. | BR-CAP-ACC-BKS-003-01 | Structured evidence | inconsistency |
FND-ACC-BKS-006 | low | The API description requires fiscal years to be removed before their unit, but implementation cascades the calendar during eligible unit deletion. | BR-CAP-ACC-BKS-001-06 | Structured evidence | inconsistency |
FND-ACC-BKS-007 | low | The unit table commentary understates project deletion dependencies and gives an obsolete default-purpose count. Current service and vocabulary behaviour differs from that commentary. | BR-CAP-ACC-BKS-001-06, BR-CAP-ACC-BKS-006-01 | Structured evidence | inconsistency |
FND-ACC-BKS-008 | medium | Installment-used payment terms reach deletion’s caller through an untranslated database failure. That contradicts the API description’s promise of useful translated refusals. | BR-CAP-ACC-BKS-011-05 | Structured evidence | defect |
FND-ACC-BKS-009 | medium | The scoped term tests do not prove deletion protection and refusal text for invoice, customer-term and installment references. The corresponding regression remains proposed. | BR-CAP-ACC-BKS-011-04, BR-CAP-ACC-BKS-011-05 | Structured evidence | debt |
FND-ACC-BKS-010 | low | Term persistence commentary describes references as future work even though financial references already exist. | CAP-ACC-BKS-011 | Structured evidence | debt |
FND-ACC-BKS-011 | medium | The console alone identifies the important missing-default purposes. Other clients receive no shared required flag, leaving a product decision about consistent early warnings. | BR-CAP-ACC-BKS-006-07, CAP-ACC-BKS-006, OQ-ACC-BKS-003 | Structured evidence | inconsistency |
FND-ACC-BKS-012 | low | Default-account selection is type-restricted in the console but accepts other types through the service. The recorded service approval does not eliminate that client difference. | BR-CAP-ACC-BKS-006-05, BR-CAP-ACC-BKS-006-08 | Structured evidence | inconsistency |
FND-ACC-BKS-013 | medium | The recorded fee decision permits unit or merchant-account rules, while only unit fee configuration is present. Product needs to settle the intended override scope. | CAP-ACC-BKS-003, OQ-ACC-BKS-002 | Structured evidence | inconsistency |
FND-ACC-BKS-014 | medium | Manual editing refusal for provider quotes has no proving scoped binding. Its acceptance scenario remains proposed. | BR-CAP-ACC-BKS-004-04 | Structured evidence | debt |
FND-ACC-BKS-015 | medium | Provider filling is demonstrated with a stub, while the scoped API test expects unavailability without a Platform client and the catalogue marks its provider journey blocked. These sources do not establish a successful live-provider run. | BR-CAP-ACC-BKS-004-05, CAP-ACC-BKS-004 | Structured evidence | debt |
FND-ACC-BKS-016 | high | Accounting still owns editable tax classes, zones and rates at these commits although the recorded realignment assigns tax determination to Commerce. Payable mapping remains embedded in the zone and shares its permission. | CAP-ACC-BKS-013, OQ-ACC-BKS-001 | Structured evidence | inconsistency |
FND-ACC-BKS-017 | low | The scoped payable-posting proof is a browser specification. The named service proof belongs to the posting module and is not independently examined here. | BR-CAP-ACC-BKS-013-02 | Structured evidence | debt |
FND-ACC-BKS-018 | medium | Document-producer adoption of the shared resolver needs examination in the owning modules. The draft’s assertion that only invoices use it is not established by the permitted Books source scope. | BR-CAP-ACC-BKS-015-08, CAP-ACC-BKS-015 | Structured evidence | inconsistency |
FND-ACC-BKS-019 | low | The shared resolver’s rejection of inactive receipt, statement and download content differs from described legacy behaviour. Its code commentary records the rationale, but no scoped product decision settles the difference. | BR-CAP-ACC-BKS-015-06 | Structured evidence | undocumented |
FND-ACC-BKS-020 | low | Several permission families publish unused actions: configuration bulk, settings creation and deletion, and payment-method deletion. Those names do not establish routes that support the actions. | BR-CAP-ACC-BKS-016-11, CAP-ACC-BKS-016 | Structured evidence | debt |
FND-ACC-BKS-021 | low | Authorized updaters can manage record locks through the service, while console configuration editors expose no lock controls. The associated catalogue journey lacks a browser specification. | BR-CAP-ACC-BKS-016-07 | Structured evidence | undocumented |
FND-ACC-BKS-022 | low | The chapter-opening catalogue still describes defaults on the unit editor. The later recorded screen change and browser specification place that work on the chart. | JNY-ACC-BKS-001 | Structured evidence | inconsistency |
FND-ACC-BKS-023 | medium | Accounting continues scheduling recurring billing preparation after Billing receives application ownership. Long-term ownership of that timing seam needs resolution. | CAP-ACC-BKS-018 | Structured evidence | debt |
FND-ACC-BKS-024 | low | Scoped records do not approve the scheduling and lifecycle capabilities as a whole. Their implementation and tests support proposed behaviour, while the initial payment-method decision confirms only its narrower subject. | CAP-ACC-BKS-018, CAP-ACC-BKS-019 | Structured evidence | undocumented |
FND-ACC-BKS-025 | low | Reconciliation approval and close bank-verification switches are stored in Accounting settings but are absent from its settings API. Their owning workflows still need an exposed change path. | BR-CAP-ACC-BKS-017-06 | Structured evidence | debt |
FND-ACC-BKS-026 | medium | Working context, concurrent currency safety, default warnings, reader controls, refund approval and payable posting have browser or observational evidence. A binding proves that assertions are present, not that a run at these commits succeeded. | BR-CAP-ACC-BKS-001-08, BR-CAP-ACC-BKS-002-08, BR-CAP-ACC-BKS-006-07, BR-CAP-ACC-BKS-016-09, BR-CAP-ACC-BKS-017-03, BR-CAP-ACC-BKS-013-02 | Structured evidence | debt |
FND-ACC-BKS-027 | low | Batch assignment, products, recurring batches and coupons share parts of configuration navigation but belong to other modules. Their inventory areas are outside this module’s replacement scope. | MOD-ACC-BKS | Structured evidence | inconsistency |
FND-ACC-BKS-028 | low | The release decision excludes stored member payment methods without explicitly settling the separately implemented configuration vocabulary. Retaining that vocabulary in release one remains an assumption. | CAP-ACC-BKS-012 | Structured evidence | undocumented |
FND-ACC-BKS-029 | low | The milestone’s top-level status and its accepted status history disagree. The history and index record acceptance while the header retains the earlier request for changes. | MOD-ACC-BKS | Structured evidence | inconsistency |
FND-ACC-BKS-030 | low | Group approvals refer in part to an external inventory unavailable in these repositories. Specific origins are retained where scoped records name the behaviour; capability-level confirmation is not a fresh approval of every discovered edge. | MOD-ACC-BKS | Structured evidence | undocumented |
FND-ACC-BKS-060 | medium | A schedule paused after repeated failures records its pause and run history but sends no attention item or notice to an accountable operator. Failure history alone does not satisfy addressed failure alerts. | TC-MON-002, WF-ACC-BKS-008, CAP-ACC-BKS-018, SVC-ACC-BKS-maintenance | Structured control evidence | control-gap |
FND-ACC-BKS-061 | medium | Administrator changes to Accounting policy retain the latest modification values but no append-only record of the prior policy, acting person and change. The last-modified stamp cannot establish protected audit evidence for these privileged changes. | TC-LOG-001, TC-LOG-002, TC-LOG-003, CAP-ACC-BKS-017, SVC-ACC-BKS-books | Structured control evidence | control-gap |
| FND-ACC-BKS-031 | medium | The resolver implementation cannot establish all its callers or missing callers outside the allowed scope. The cross-producer claim remains unknown pending an owning-module examination. | BR-CAP-ACC-BKS-015-08 | Structured evidence | undocumented |
| FND-ACC-BKS-032 | low | Thirty-two existing service test files lack row-level draft bindings. The examination gives every file a capability evidence home and lists the remaining binding gap explicitly. | MOD-ACC-BKS | Structured evidence | debt |
| FND-ACC-BKS-033 | low | A currency-read comment claims key-share locking that its query does not request. Foreign-key protection and a racing-request specification support the safety result without establishing that described lock order. | BR-CAP-ACC-BKS-002-08 | Structured evidence | inconsistency |
| FND-ACC-BKS-034 | medium | The new zero-tender, receiving-account dependency, owned-schedule mutation and export-dispatch scenarios are proposed. Complete proving bindings remain work to do before approval. | BR-CAP-ACC-BKS-003-09, BR-CAP-ACC-BKS-007-09, BR-CAP-ACC-BKS-018-10, BR-CAP-ACC-BKS-019-09 | Structured evidence | debt |
| FND-ACC-BKS-035 | medium | The draft promises that any updater can clear record locks. A full GL lock prevents the ordinary update from reaching lock changes, and fiscal-year and settings updates do not expose lock mutation. Product needs a defined release path before relying on this configuration safeguard. | BR-CAP-ACC-BKS-016-07 | Structured evidence | inconsistency | | FND-ACC-BKS-036 | high | Replacing a tax zone deletes its rates and writes new ones under new identities. Issued documents keep only a loose reference to the old rate, so a document issued before the change and posted after it finds no payable mapping and posts its tax to the unit's sales-tax default, or is refused when the unit has none, with no warning. | WF-ACC-BKS-006, CAP-ACC-BKS-013, BR-CAP-ACC-BKS-013-02, BR-CAP-ACC-BKS-013-05, ADR-ACC-BKS-010, OQ-ACC-BKS-005 | Structured evidence | defect | | FND-ACC-BKS-037 | medium | The accounting-method guard counts the current open period's posted and downloaded batches with a plain read inside the unit's transaction. A batch posted concurrently in that period is not seen, so a method change can commit against posted work. | WF-ACC-BKS-002, STATE-ACC-BKS-001, BR-CAP-ACC-BKS-003-01 | Structured evidence | defect | | FND-ACC-BKS-038 | medium | Batches, billing, close, products, reconciliation and transactions import the Books tables and persistence functions and read them directly. No declared read contract exists, so the Service Contract cannot list these reads and a Books schema change is a change to every consumer. | SVC-ACC-BKS-books, ADR-ACC-BKS-001, RESP-ACC | Structured evidence | debt | | FND-ACC-BKS-039 | medium | Books configuration publishes no change events and keeps no revision history. Changes to default accounts, payment methods or refund approval leave only the last-modified stamp. | ADR-ACC-BKS-014, OQ-ACC-BKS-004, DOM-ACC-BKS-006 | Structured evidence | undocumented | | FND-ACC-BKS-040 | low | Refund approval, overpayment handling, deferral truncation and the service-period requirement have no console control. The console's settings model carries only the statement default, and its save leaves the other values unchanged. | CAP-ACC-BKS-017, SCR-ACC-BKS-013, BR-CAP-ACC-BKS-017-03 | Structured evidence | debt | | FND-ACC-BKS-041 | low | The business unit editor offers neither the tender fee rule and default fee policy nor the direct write-off treatment. They can be set only through the API, and console saves keep them as stored. | CAP-ACC-BKS-003, SCR-ACC-BKS-001, WF-ACC-BKS-002 | Structured evidence | debt | | FND-ACC-BKS-042 | medium | Among the cited producers, only invoice rendering calls the shared template resolver. The statement action accepts its own template choice without calling it, so the resolution order is not yet uniform. | WF-ACC-BKS-007, ADR-ACC-BKS-013, BR-CAP-ACC-BKS-015-08, FND-ACC-BKS-031 | Structured evidence | inconsistency | | FND-ACC-BKS-043 | low | The Accounting workspace object spans two source modules: Books holds the shared definitions and settings, and maintenance holds schedules and lifecycle participation. The design names Books as the single owner and maintenance as a reader. | DOM-ACC-BKS-006, SVC-ACC-BKS-maintenance | Structured evidence | inconsistency | | FND-ACC-BKS-044 | low | The Platform standards and shared-library source repository are absent from this checkout, so their architecture citations remain unverified. Independent examination inspected the locked installed HTTP and schedules packages and resolved health operation identifiers, dispatch, consumer and recurrence behavior. Those observations do not approve the cited standards. | ADR-ACC-BKS-005, ADR-ACC-BKS-011, ADR-ACC-BKS-012, ADR-ACC-BKS-015, SVC-ACC-BKS-books, SVC-ACC-BKS-maintenance | Structured evidence | undocumented | | FND-ACC-BKS-045 | low | The module asks no model, so it has no inference artifacts. The module charter lacks the one-sentence statement the conventions require, and that correction belongs to the planning layer. | MOD-ACC-BKS | Structured evidence | debt | | FND-ACC-BKS-046 | low | The maintenance module's configuration participant declares, purges and exports Products and Batch tables as well as Books tables. The lifecycle declarations for those records do not live with their owners. | WF-ACC-BKS-010, WF-ACC-BKS-011, SVC-ACC-BKS-maintenance | Structured evidence | debt | | FND-ACC-BKS-047 | low | The provider fill reads each currency's rate source before calling the provider and does not re-read it before writing. A currency switched to manual rates during a fill can still receive a provider row. | WF-ACC-BKS-004, BR-CAP-ACC-BKS-004-05 | Structured evidence | defect | | FND-ACC-BKS-048 | low | A schedule paused after five failures raises no attention item or notice. The pause appears only on the owning record's schedule summary and in run history. | WF-ACC-BKS-008, STATE-ACC-BKS-004, BR-CAP-ACC-BKS-018-07 | Structured evidence | undocumented | | FND-ACC-BKS-049 | low | Independent examination resolves the earlier anchor finding: export dispatch is an executable function in the pinned source, and the existing planning citation reaches it. No planning correction is needed for that symbol. | BR-CAP-ACC-BKS-019-09, WF-ACC-BKS-011 | Structured evidence | inconsistency |
| FND-ACC-BKS-050 | medium | The named design brief is absent, and the planning records remain drafts. Examination establishes fidelity to the available planning baseline, without treating it as Andrew’s approval. | MOD-ACC-BKS | Structured evidence | undocumented | | FND-ACC-BKS-051 | medium | The draft turns creation-time and request-time checks into permanent guarantees: fiscal years can subsequently be deleted, and a fee product is checked only when a request names it. The design now states those limits; the unchanged planning baseline still needs review before approval. | DOM-ACC-BKS-001, STATE-ACC-BKS-001, RESP-ACC | Structured evidence | inconsistency | | FND-ACC-BKS-052 | medium | Accounting’s availability gate observes workspace states but does not establish Platform’s allowed transitions, cancellation policy or completion guards. Those moves remain unknown until the owning module supplies its lifecycle contract. | STATE-ACC-BKS-005 | Structured evidence | undocumented | | FND-ACC-BKS-053 | low | The draft applies shared-list patterns to dedicated pages and claims confirmation for status changes. The console changes status immediately, hides inactive rows by default and has dedicated fiscal-year and template-editor pages. Contracts now distinguish these behaviors and the whole-day console restriction on payment terms. | SCR-ACC-BKS-001, SCR-ACC-BKS-002, SCR-ACC-BKS-008, SCR-ACC-BKS-009, SCR-ACC-BKS-014 | Structured evidence | inconsistency | | FND-ACC-BKS-054 | high | A unique run record does not guarantee one handler execution. Redelivery restarts a running occurrence, and concurrent duplicate deliveries can both enter the handler; terminal runs are skipped. Handler idempotency remains an owning-module obligation rather than a scheduler guarantee. | WF-ACC-BKS-008, STATE-ACC-BKS-004, DOM-ACC-BKS-006, SVC-ACC-BKS-maintenance | Structured evidence | defect | | FND-ACC-BKS-055 | high | The dispatcher commits the claim and advances timing before publication. Explicitly refused messages are released, but a process failure after commit and before publication or release can leave a queued run marked as offered with no message and no automatic recovery in the examined dispatcher. | WF-ACC-BKS-008, SVC-ACC-BKS-maintenance | Structured evidence | defect | | FND-ACC-BKS-056 | medium | Export’s creation cut-off filters eligible records but does not freeze their values across batches or retries. Updates and deletions can change an exported part, and embedded collections follow their own declared cut-off; the contract now limits repeatability to the staging location and cursor. | WF-ACC-BKS-011, SVC-ACC-BKS-maintenance | Structured evidence | debt | | FND-ACC-BKS-057 | low | Several draft choices claim more authority than their cited origins provide, including exclusive Books writing, universal database protection and absence of external demand for change events. The final records describe scoped observations and proposed alternatives without treating them as newly approved product decisions. | ADR-ACC-BKS-001, ADR-ACC-BKS-003, ADR-ACC-BKS-004, ADR-ACC-BKS-014, ADR-ACC-BKS-015, RESP-ACC | Structured evidence | undocumented |
| FND-ACC-BKS-058 | medium | Account currency is locked by the console editor but is not a write-once service field. The service accepts another currency enabled for the unit, subject to restricting references. The draft confused the screen restriction with a permanent domain invariant; Product should settle whether other clients should have the same restriction. | DOM-ACC-BKS-002, ADR-ACC-BKS-003, SCR-ACC-BKS-003 | Structured evidence | inconsistency |
| FND-ACC-BKS-059 | medium | The tax-class screen also edits and clears product-type defaults, actions omitted from the draft. Its Save control uses update permission for both actions, but the clear route requires delete permission, so an updater without delete permission can be offered an action the service refuses. The corrected screen contract records both gates and keeps ownership with Products. | SCR-ACC-BKS-012 | Structured evidence | defect | | FND-ACC-BKS-062 | medium | The capability has proposed tests awaiting executable proof. Lifecycle transitions require individual execution bindings. The bound working-context example does not visit a separate scoped list. | ATS-ACC-BKS-001, CAP-ACC-BKS-001 | Structured evidence | coverage-gap | | FND-ACC-BKS-063 | medium | The capability has proposed tests awaiting executable proof and unresolved category coverage. | ATS-ACC-BKS-002, CAP-ACC-BKS-002 | Structured evidence | coverage-gap | | FND-ACC-BKS-064 | medium | The capability has proposed tests awaiting executable proof and unresolved category coverage. Method changes racing current-period posting have no established coordinated outcome; the version-race scenario covers only competing replacements. | ATS-ACC-BKS-003, CAP-ACC-BKS-003 | Structured evidence | coverage-gap | | FND-ACC-BKS-065 | medium | The capability has proposed tests awaiting executable proof and unresolved category coverage. Provider filling racing a source switch or repeated provider calls has no complete executable proof. | ATS-ACC-BKS-004, CAP-ACC-BKS-004 | Structured evidence | coverage-gap | | FND-ACC-BKS-066 | medium | The capability has proposed tests awaiting executable proof and unresolved category coverage. The complete fixed-currency expectation conflicts with the examined service guard. | ATS-ACC-BKS-005, CAP-ACC-BKS-005 | Structured evidence | coverage-gap | | FND-ACC-BKS-067 | medium | The capability has proposed tests awaiting executable proof and unresolved category coverage. | ATS-ACC-BKS-006, CAP-ACC-BKS-006 | Structured evidence | coverage-gap | | FND-ACC-BKS-068 | medium | The capability has proposed tests awaiting executable proof and unresolved category coverage. | ATS-ACC-BKS-007, CAP-ACC-BKS-007 | Structured evidence | coverage-gap | | FND-ACC-BKS-069 | medium | The capability has proposed tests awaiting executable proof and unresolved category coverage. | ATS-ACC-BKS-008, CAP-ACC-BKS-008 | Structured evidence | coverage-gap | | FND-ACC-BKS-070 | medium | The capability has proposed tests awaiting executable proof and unresolved category coverage. Lifecycle transitions require individual execution bindings. Generation racing year deletion or Close remains unproved beyond serial generation planning. | ATS-ACC-BKS-009, CAP-ACC-BKS-009 | Structured evidence | coverage-gap | | FND-ACC-BKS-071 | medium | The capability has proposed tests awaiting executable proof and unresolved category coverage. Lifecycle transitions require individual execution bindings. | ATS-ACC-BKS-010, CAP-ACC-BKS-010 | Structured evidence | coverage-gap | | FND-ACC-BKS-072 | medium | The capability has proposed tests awaiting executable proof and unresolved category coverage. | ATS-ACC-BKS-011, CAP-ACC-BKS-011 | Structured evidence | coverage-gap | | FND-ACC-BKS-073 | medium | The capability has proposed tests awaiting executable proof and unresolved category coverage. | ATS-ACC-BKS-012, CAP-ACC-BKS-012 | Structured evidence | coverage-gap | | FND-ACC-BKS-074 | medium | The capability has proposed tests awaiting executable proof and unresolved category coverage. | ATS-ACC-BKS-013, CAP-ACC-BKS-013 | Structured evidence | coverage-gap | | FND-ACC-BKS-075 | medium | The capability has proposed tests awaiting executable proof and unresolved category coverage. Lifecycle transitions require individual execution bindings. | ATS-ACC-BKS-014, CAP-ACC-BKS-014 | Structured evidence | coverage-gap | | FND-ACC-BKS-076 | medium | The capability has proposed tests awaiting executable proof and unresolved category coverage. Lifecycle transitions require individual execution bindings. | ATS-ACC-BKS-015, CAP-ACC-BKS-015 | Structured evidence | coverage-gap | | FND-ACC-BKS-077 | medium | The capability has proposed tests awaiting executable proof and unresolved category coverage. | ATS-ACC-BKS-016, CAP-ACC-BKS-016 | Structured evidence | coverage-gap | | FND-ACC-BKS-078 | medium | The capability has proposed tests awaiting executable proof and unresolved category coverage. Required service-period issuance is outside the examined consuming-module implementation; omission coverage proves only the stored policy. The reconciliation assertion does not read the close-verification switch. | ATS-ACC-BKS-017, CAP-ACC-BKS-017 | Structured evidence | coverage-gap | | FND-ACC-BKS-079 | medium | The capability has proposed tests awaiting executable proof and unresolved category coverage. Lifecycle transitions require individual execution bindings. Single run identity does not prove one handler execution for redelivered or concurrent messages. | ATS-ACC-BKS-018, CAP-ACC-BKS-018 | Structured evidence | coverage-gap | | FND-ACC-BKS-080 | medium | The capability has proposed tests awaiting executable proof and unresolved category coverage. Lifecycle transitions require individual execution bindings. Cross-batch export consistency and purge cancellation races lack a full executable qualification. | ATS-ACC-BKS-019, CAP-ACC-BKS-019 | Structured evidence | coverage-gap | | FND-ACC-BKS-081 | high | The chart identity test combines code and unit refusals with a fixed-currency expectation. The service guard fixes code and unit but accepts supported currency input, while the database test expects a currency refusal; the full scenario remains proposed until runtime conformance resolves the conflict. | CAP-ACC-BKS-005, ATS-ACC-BKS-005-02 | Structured evidence | inconsistency | | FND-ACC-BKS-082 | medium | Feature acceptance includes proposed joined outcomes that no existing executable suite proves in full. Existing capability tests do not establish these feature regressions or their combined permission coverage. | FAS-ACC-BKS-01, FAS-ACC-BKS-02, FAS-ACC-BKS-03, FAS-ACC-BKS-04, FAS-ACC-BKS-05, FAS-ACC-BKS-06 | Structured evidence | coverage-gap | | FND-ACC-BKS-083 | medium | Registered suites without scenario bindings remain executable evidence awaiting an assertion-to-specification mapping. Registration does not imply that their assertions cover an acceptance scenario. | TST-ACC-BKS-008, TST-ACC-BKS-010, TST-ACC-BKS-019, TST-ACC-BKS-023, TST-ACC-BKS-026, TST-ACC-BKS-028, TST-ACC-BKS-029, TST-ACC-BKS-030, TST-ACC-BKS-031, TST-ACC-BKS-032, TST-ACC-BKS-033, TST-ACC-BKS-034, TST-ACC-BKS-035, TST-ACC-BKS-036, TST-ACC-BKS-037, TST-ACC-BKS-038, TST-ACC-BKS-039, TST-ACC-BKS-040, TST-ACC-BKS-041, TST-ACC-BKS-042, TST-ACC-BKS-059, TST-ACC-BKS-062, TST-ACC-BKS-065, TST-ACC-BKS-071, TST-ACC-BKS-073, TST-ACC-BKS-075, TST-ACC-BKS-076, TST-ACC-BKS-077, TST-ACC-BKS-079, TST-ACC-BKS-081, TST-ACC-BKS-083, TST-ACC-BKS-088, TST-ACC-BKS-090, TST-ACC-BKS-092, TST-ACC-BKS-094, TST-ACC-BKS-095, TST-ACC-BKS-096, TST-ACC-BKS-097, TST-ACC-BKS-101, TST-ACC-BKS-103, TST-ACC-BKS-104, TST-ACC-BKS-105, TST-ACC-BKS-106, TST-ACC-BKS-107, TST-ACC-BKS-108, TST-ACC-BKS-109, TST-ACC-BKS-110, TST-ACC-BKS-111, TST-ACC-BKS-112, TST-ACC-BKS-113, TST-ACC-BKS-114, TST-ACC-BKS-115, TST-ACC-BKS-116, TST-ACC-BKS-117, TST-ACC-BKS-118, TST-ACC-BKS-119, TST-ACC-BKS-120, TST-ACC-BKS-121, TST-ACC-BKS-122, TST-ACC-BKS-123, TST-ACC-BKS-124, TST-ACC-BKS-125, TST-ACC-BKS-126, TST-ACC-BKS-127, TST-ACC-BKS-128, TST-ACC-BKS-129, TST-ACC-BKS-130, TST-ACC-BKS-131, TST-ACC-BKS-132, TST-ACC-BKS-133, TST-ACC-BKS-134, TST-ACC-BKS-135, TST-ACC-BKS-136, TST-ACC-BKS-137, TST-ACC-BKS-138, TST-ACC-BKS-139, TST-ACC-BKS-140, TST-ACC-BKS-141, TST-ACC-BKS-142, TST-ACC-BKS-143, TST-ACC-BKS-144, TST-ACC-BKS-145, TST-ACC-BKS-146, TST-ACC-BKS-147, TST-ACC-BKS-148, TST-ACC-BKS-149, TST-ACC-BKS-150, TST-ACC-BKS-151, TST-ACC-BKS-152, TST-ACC-BKS-153, TST-ACC-BKS-154, TST-ACC-BKS-155, TST-ACC-BKS-156, TST-ACC-BKS-157, TST-ACC-BKS-158, TST-ACC-BKS-159, TST-ACC-BKS-160, TST-ACC-BKS-161, TST-ACC-BKS-162, TST-ACC-BKS-164, TST-ACC-BKS-166, TST-ACC-BKS-169, TST-ACC-BKS-176, TST-ACC-BKS-179, TST-ACC-BKS-182, TST-ACC-BKS-184, TST-ACC-BKS-185, TST-ACC-BKS-186, TST-ACC-BKS-188, TST-ACC-BKS-189, TST-ACC-BKS-190, TST-ACC-BKS-191, TST-ACC-BKS-192, TST-ACC-BKS-193, TST-ACC-BKS-196, TST-ACC-BKS-197 | Structured evidence | coverage-gap | | FND-ACC-BKS-084 | medium | Several cumulative journey scenarios bind independent runs with separate fixture records. Those suites provide component assertions but do not execute the complete journey on one shared set of records. | ATS-ACC-BKS-001-08, ATS-ACC-BKS-002-08, ATS-ACC-BKS-016-10 | Structured evidence | coverage-gap | | FND-ACC-BKS-085 | low | The earlier term scenario describes thirty days, while its bound browser run edits a forty-five-day term to forty-six days before issuance. The corrected scenario matches that run and its subsequent zero-day selection. | ATS-ACC-BKS-011-04 | Structured evidence | inconsistency |
Open Questions
| id | question | why_it_matters | options | recommendation | affects |
|---|---|---|---|---|---|
OQ-ACC-BKS-001 | How does Accounting handle its tax configuration until Commerce takes ownership, and how is payable mapping retained? | Unsettled ownership can give checkout and staff invoices different tax treatment and can lose liability destinations during migration. | A: retain editable setup until Commerce is ready, then migrate it while keeping separate Accounting mapping. B: make Accounting setup read-only immediately. C: keep Accounting setup for staff documents indefinitely. | The product should choose A and separate payable mapping before moving determination. | CAP-ACC-BKS-013, FND-ACC-BKS-016 |
OQ-ACC-BKS-002 | Does merchant configuration need a fee override or should all fees use unit policy? | Different processors can have different costs, and an override changes how a tender selects policy. | A: use unit policy for release one and record the amended scope. B: allow merchant overrides. C: move all policy to merchants. | The product should choose A for release one and revisit overrides for a demonstrated multi-processor need. | CAP-ACC-BKS-003, FND-ACC-BKS-013 |
OQ-ACC-BKS-003 | Should the service identify required default purposes and what should missing defaults prevent? | A console-only list cannot give other clients the same early configuration warning. | A: publish required purposes for shared warnings. B: retain the console list. C: add posting refusal checks alongside shared warnings. | The product should choose A while preserving the decision that invoice issue does not wait for account configuration. | CAP-ACC-BKS-006, FND-ACC-BKS-011 |
OQ-ACC-BKS-004 | Should changes to the books configuration keep a revision history of who changed what and from what? | Default accounts, payment methods, fee rules and refund approval change where and how money is booked, but today only the last change's time and person are kept, so an auditor cannot reconstruct a past setting. | A: adopt Platform's record history for units, accounts, defaults, methods, tax mapping and settings. B: keep last-modified stamps only. C: record history only for policy fields that change money behaviour. | The product should choose A for units, chart records, defaults and settings, written at commit as CRM does, so finance changes are auditable. | ADR-ACC-BKS-014, FND-ACC-BKS-039, DOM-ACC-BKS-006 |
OQ-ACC-BKS-005 | When a tax zone is changed, which payable account should documents issued before the change post their tax to? | Posting looks up the payable account by rate when the batch is posted, and a zone change gives every rate a new identity, so liability for already-issued documents can silently move to the unit default. | A: keep rate identities stable across a replacement (update rates in place, new identities only for new rates). B: store the payable account on each tax line at issue. C: accept the fall-back to the unit default and warn on the zone screen. | The product should choose A, which keeps accounts resolved at posting as decided and survives the move of tax setup to Commerce if payable mapping moves to its own record. | WF-ACC-BKS-006, FND-ACC-BKS-036, CAP-ACC-BKS-013, ADR-ACC-BKS-010 |
OQ-ACC-BKS-006 | What delivery recovery and repeat-safety guarantees must scheduled handlers provide? | A claimed occurrence can be stranded without a message, and unfinished work can execute more than once. | A: durable publication recovery plus explicit handler idempotency. B: expiring run leases with owner recovery. C: accept the current limits and provide manual recovery. | Choose A and prove each registered handler’s response to duplicate delivery and interruption after commit. | WF-ACC-BKS-008, FND-ACC-BKS-054, FND-ACC-BKS-055 |
OQ-ACC-BKS-007 | Must workspace export represent a stable snapshot or current values read during each batch? | Creation cutoffs do not freeze values, so retries and later batches can describe different configurations. | A: provide a stable snapshot contract. B: retain current-value export with documented limitations. C: coordinate a write freeze during export. | Product should choose the promised consistency level before implementation preparation; no snapshot guarantee should be inferred from the current cutoff. | WF-ACC-BKS-011, FND-ACC-BKS-056 |
OQ-ACC-BKS-008 | Should account currency changes be permitted consistently across clients? | The console locks account currency while the service accepts a supported change when references permit it. | A: make currency immutable in the service and database. B: expose a guarded console change. C: retain the client difference explicitly. | Settle the product rule before changing either enforcement or the editor, and preserve existing reference protection. | DOM-ACC-BKS-002, SCR-ACC-BKS-003, FND-ACC-BKS-058 |