FND-ACC-PRD-001 | medium | Configuration hosts the Products screens, but the original registry points to absent Accounting routes. The original scope also omits the products guide cited throughout the source. The corrected registry includes these locations. | MOD-ACC-PRD | Structured evidence | inconsistency |
FND-ACC-PRD-002 | high | The approved realignment assigns product tax configuration to Commerce. Accounting still implements product-kind defaults and the setup’s tax assignment, so the current capability remains recorded as out of scope for the future boundary. The transition still needs a detailed plan. | CAP-ACC-PRD-018, CAP-ACC-PRD-015, BR-CAP-ACC-PRD-015-06, BR-CAP-ACC-PRD-018-10 | Structured evidence | inconsistency |
FND-ACC-PRD-003 | low | The milestone and its index disagree about acceptance: their status summaries retain Changes Requested while acceptance entries record Product Accepted. Named product decisions remain usable evidence, but the record’s overall state needs clarification. | MOD-ACC-PRD | Structured evidence | inconsistency |
FND-ACC-PRD-004 | low | The products guide describes a backend-only catalogue and a bundle-only deletion restriction. The console already hosts catalogue screens, and transaction and installment references also restrict deletion. The guide needs reconciliation with the implementation. | CAP-ACC-PRD-003, CAP-ACC-PRD-006 | Structured evidence | inconsistency |
FND-ACC-PRD-005 | medium | A migrated special-price audience remains admissible before Commerce’s audience table exists. Once that table exists, the audience must be active there; otherwise even an unrelated product edit is refused. This conflicts with the migration record’s assumption that held audiences remain editable. | BR-CAP-ACC-PRD-009-05, CAP-ACC-PRD-008, OQ-ACC-PRD-002 | Structured evidence | defect |
FND-ACC-PRD-006 | medium | The database blocks deletion for discount-product and installment references, but the refusal translator handles only the invoice’s ordinary product reference. These other restrictions can surface as server errors. Neither case has dedicated product-module proof. | BR-CAP-ACC-PRD-006-02 | Structured evidence | defect |
FND-ACC-PRD-007 | medium | Console saving has separate product and accounting stages. A later setup refusal leaves the earlier product save in place and reports partial completion. The product API exposes no combined transaction for these two records. | CAP-ACC-PRD-015, CAP-ACC-PRD-002, JNY-ACC-PRD-001 | Structured evidence | undocumented |
FND-ACC-PRD-008 | medium | Console setup serialization omits revenue-split identities, so saving assigns new identities instead of retaining those supplied by service clients. This can disrupt identity-based reconciliation with posting history; the cross-module consequence needs explicit proof. | BR-CAP-ACC-PRD-016-07, BR-CAP-ACC-PRD-016-10 | Structured evidence | defect |
FND-ACC-PRD-009 | medium | HTTP replacement clears omitted optional product properties, while the database domain-save function preserves omitted values. The two entry points therefore implement different edit contracts for the same catalogue record. | BR-CAP-ACC-PRD-007-08, BR-CAP-ACC-PRD-004-02, OQ-ACC-PRD-003 | Structured evidence | inconsistency |
FND-ACC-PRD-010 | low | Products bulk access and product-accounting create and bulk access are declared permissions without matching routes. Bulk setup replacement instead requires update access. Role configuration can expose these inactive powers. | CAP-ACC-PRD-002, CAP-ACC-PRD-015, CAP-ACC-PRD-017 | Structured evidence | debt |
FND-ACC-PRD-011 | low | Template cleanup happens after product deletion and logs failures without restoring the product. A product commit failure after successful template saving also leaves a remote change. The implementation has no compensation for either window. | BR-CAP-ACC-PRD-006-06, BR-CAP-ACC-PRD-014-04 | Structured evidence | debt |
FND-ACC-PRD-012 | low | Several implementation comments attribute details to an unnamed product-owner direction without a decision identifier. Those comments establish documentation, but readable identities, account-slot restrictions and selling details stay proposed unless an identifiable approved decision covers them. | BR-CAP-ACC-PRD-002-01, BR-CAP-ACC-PRD-002-10, BR-CAP-ACC-PRD-015-04, CAP-ACC-PRD-012, CAP-ACC-PRD-013, CAP-ACC-PRD-014 | Structured evidence | undocumented |
FND-ACC-PRD-013 | low | Earlier acceptance records still describe domain-kind tabs, console creation of Legacy Products, obsolete custom fields and bundle totals without quantity. Some journey text also describes a defect its browser spec reports fixed. The specification follows current code and named decisions rather than copying these obsolete expectations. | BR-CAP-ACC-PRD-001-07, BR-CAP-ACC-PRD-011-06, BR-CAP-ACC-PRD-002-13 | Structured evidence | inconsistency |
FND-ACC-PRD-014 | low | Earlier acceptance capability identifiers collide with this corpus’s identifiers while describing different scopes. Predecessor references retain a corpus prefix so readers can distinguish the two histories. | MOD-ACC-PRD | Structured evidence | inconsistency |
FND-ACC-PRD-015 | low | The console requires receivables and restricts relative deferral ranges more than the service does. It rejects ranges extending past December and year offsets beyond ten; backend rules allow larger offsets. An API-created setup can consequently be impossible to resave through the console. | BR-CAP-ACC-PRD-015-14, BR-CAP-ACC-PRD-016-10 | Structured evidence | inconsistency |
FND-ACC-PRD-016 | low | Task assignment validates identifier syntax without confirming the user exists. A syntactically valid unknown assignee can be stored. | BR-CAP-ACC-PRD-013-03 | Structured evidence | debt |
FND-ACC-PRD-017 | low | Price validation accepts pricing-period identifiers without checking Commerce’s schedule registry. A spelling error can therefore create an unrecognized period assignment. | CAP-ACC-PRD-008 | Structured evidence | debt |
FND-ACC-PRD-018 | low | Accounting setup replacement remains available for a retired product even though product editing is refused. The records provide no explicit decision about that difference. | BR-CAP-ACC-PRD-015-15 | Structured evidence | undocumented |
FND-ACC-PRD-019 | low | The refusal translator retains a removed custom-field constraint name, and some test titles retain the older UUID identity terminology. These remnants need cleanup in the owning implementation. | CAP-ACC-PRD-002 | Structured evidence | debt |
FND-ACC-PRD-020 | low | Application ownership is checked in product write logic, but the HTTP routes admit console callers only. Domain services currently use the database write functions rather than these HTTP routes. | BR-CAP-ACC-PRD-007-01 | Structured evidence | undocumented |
FND-ACC-PRD-021 | low | The service continues accepting and returning the deprecated audience alias alongside audience identifiers. The console already uses identifiers, and the migration record leaves alias removal undecided. | BR-CAP-ACC-PRD-008-14 | Structured evidence | debt |
FND-ACC-PRD-022 | low | No bound replacement test establishes cross-workspace body rejection and complete ignoring of derived values. The cited browser spec exercises creation, and mapper unit cases cover lock mapping. The replacement scenario is now proposed and needs direct API proof. | BR-CAP-ACC-PRD-004-09 | Structured evidence | debt |
FND-ACC-PRD-023 | low | The API supports finding missing setups and replacing setups in bulk. The console has a missing-setup indicator but exposes neither of those administration workflows. | BR-CAP-ACC-PRD-017-07 | Structured evidence | undocumented |
FND-ACC-PRD-024 | low | The reviewed console hides sale windows, portal visibility, purchase limits, confirmation settings, bundles and cancellation fees. The API retains these settings, while the products guide fails to distinguish their availability from the visible editor. | CAP-ACC-PRD-011, CAP-ACC-PRD-012, CAP-ACC-PRD-014, BR-CAP-ACC-PRD-004-10 | Structured evidence | inconsistency |
FND-ACC-PRD-025 | medium | Capability-wide confirmation makes uncited implementation details appear approved. Capabilities, concepts, features and journeys now remain proposed; individual rules retain authority only through their recorded origins. | MOD-ACC-PRD | Structured evidence | inconsistency |
FND-ACC-PRD-026 | medium | Several bound scenarios claim additional actions their tests do not execute. Older-identity replacement does not prove deletion; the feature-preservation browser spec skips confirmation e-mail and does not assert availability fields; the pricing-audience query test does not perform a product edit. Narrowed scenarios retain genuine bindings; register authorization denial, all price precision boundaries, all-time purchase clearing, and assignee existence remain outside those bindings. Replacement workspace and derived-field proof is now proposed because its former browser binding only tests creation. | CAP-ACC-PRD-002, CAP-ACC-PRD-004, CAP-ACC-PRD-009 | Structured evidence | debt |
FND-ACC-PRD-027 | medium | The domain browser spec skips database saves and rollbacks, so an empty product list there proves no transaction rollback. Accounting’s integration suite proves saving and reads but a failure after saving a domain extension still needs an executable cross-service proof. | BR-CAP-ACC-PRD-007-04, JNY-ACC-PRD-006 | Structured evidence | debt |
FND-ACC-PRD-028 | low | Tax-default update and delete locks differ: a delete-only lock permits replacement, and an update lock cannot be cleared through replacement. The existing locked-default test covers the combined lock; delete-only behavior needs separate proof. | BR-CAP-ACC-PRD-018-07 | Structured evidence | undocumented |
FND-ACC-PRD-029 | medium | Product exports and read-only metadata registration lack a capability in the draft. The added export capability records their declarations; no in-scope product test exercises actual export delivery, cutoff behavior or embedded collection completeness. | CAP-ACC-PRD-019, BR-CAP-ACC-PRD-019-01, BR-CAP-ACC-PRD-019-02, BR-CAP-ACC-PRD-019-03, BR-CAP-ACC-PRD-019-04 | Structured evidence | debt |
FND-ACC-PRD-030 | low | Draft coverage counts are inaccurate: the module contains six end-to-end files, thirteen integration files, two current unit files and twenty-one carried spec files, rather than the sixteen carried files the charter claims. The examination reports physical files separately from test bindings. Twenty carried files remain without a direct planning binding, although their adapted behavior falls within existing catalogue and accounting capabilities. | MOD-ACC-PRD | Structured evidence | inconsistency |
FND-ACC-PRD-031 | low | The registry-size refusal and accounting child-collection limits are must-prove refusals without bound scenarios. Existing rule rows now identify the requirement, and this finding retains the missing boundary proofs. | BR-CAP-ACC-PRD-001-05, BR-CAP-ACC-PRD-016-09 | Structured evidence | debt |
FND-ACC-PRD-032 | medium | Catalog configuration alone does not prove price conversion, task creation, purchase-limit enforcement, confirmation sending, invoice preservation or posting. Documented downstream responsibilities now have no claimed enforcement point in this module. The existing posting browser spec proves default resolution and preservation after setup changes; it now has a dedicated bound scenario. Other downstream effects still need contracts and executable cross-module proofs. | CAP-ACC-PRD-005, CAP-ACC-PRD-009, CAP-ACC-PRD-010, CAP-ACC-PRD-011, CAP-ACC-PRD-012, CAP-ACC-PRD-013, CAP-ACC-PRD-014, CAP-ACC-PRD-015, CAP-ACC-PRD-018 | Structured evidence | debt |
FND-ACC-PRD-033 | low | The console evaluates price windows using date strings and includes the end boundary, while backend validation uses instants with an exclusive end. The console also requires a current always standard base price, whereas backend validation accepts a standard base price in a named period. These differences need price-boundary and period-only tests before a shared editor contract is settled. | CAP-ACC-PRD-008 | Structured evidence | inconsistency |
FND-ACC-PRD-034 | medium | The latest domain-save function still defaults omitted component prices to zero and sums allocations without quantity, while HTTP writes require a component price and multiply by quantity. It also admits held audiences after Commerce activation where HTTP writes require active audiences. Existing parity tests omit these divergent variants. The added rule rows describe the database contract without assigning it approval. | CAP-ACC-PRD-007, CAP-ACC-PRD-011, CAP-ACC-PRD-009 | Structured evidence | inconsistency |
FND-ACC-PRD-035 | low | No model invocation appears in the examined product service or screens. Service, workflow and screen contracts therefore declare empty inference lists. The required no-inference sentence is still absent from the charter, which this job cannot edit. | MOD-ACC-PRD, SVC-ACC-PRD-products | Structured evidence | undocumented |
FND-ACC-PRD-036 | medium | Catalogue records have modification stamps but no declared revision history or change events. Finance cannot reconstruct earlier prices or account settings from those current records, and shared readers receive no announced changes. | DOM-ACC-PRD-001, DOM-ACC-PRD-004, ADR-ACC-PRD-015, OQ-ACC-PRD-004 | Structured evidence | debt |
FND-ACC-PRD-037 | low | Platform's persistence, queue, job, history, security and indexing standards remain unavailable within this job's three-repository access. Accounting references those standards, but those references do not establish conformance; design authority remains proposed where a standard would be required. | SVC-ACC-PRD-products, ADR-ACC-PRD-005, ADR-ACC-PRD-013 | Structured evidence | undocumented |
FND-ACC-PRD-038 | low | Product replacement holds its row lock while waiting for Platform template saving or clearing and while assembling the response. Remote latency therefore delays other writes of that product and its setup. | WF-ACC-PRD-001, ADR-ACC-PRD-008, STATE-ACC-PRD-004 | Structured evidence | debt |
FND-ACC-PRD-039 | low | Setup deletion is exposed by the service and console adapter but no examined product screen invokes it. Staff cannot use this editor to remove a setup and return to unit-default treatment. | BR-CAP-ACC-PRD-015-10, SCR-ACC-PRD-003, STATE-ACC-PRD-003 | Structured evidence | undocumented |
FND-ACC-PRD-040 | medium | Quick Activate and Deactivate submit product replacement without loaded sale-window or portal-visibility values. Replacement clears those omissions, so a status action can erase the window and restore visibility for a hidden product. The editor retains them. This consequence is inferred from source and has no direct test. | BR-CAP-ACC-PRD-004-10, BR-CAP-ACC-PRD-005-01, SCR-ACC-PRD-001, ADR-ACC-PRD-006 | Structured evidence | defect |
FND-ACC-PRD-041 | medium | The realignment architecture reports that quotes ignore kind tax defaults while issue applies them. Product resolution also prefers setup class, then kind default. The reported consumer difference remains unproved in this module and must be resolved during tax ownership transfer. | INV-DOM-ACC-PRD-004-11, BR-CAP-ACC-PRD-018-01, ADR-ACC-PRD-011 | Structured evidence | inconsistency |
FND-ACC-PRD-042 | low | The documented table readers include Commerce, Transactions, Billing and Batch Management, whose service contracts are absent from this corpus. Their reader lists and schema dependencies therefore remain incomplete; this job has not verified each downstream implementation. | DOM-ACC-PRD-001, DOM-ACC-PRD-002, DOM-ACC-PRD-004, ADR-ACC-PRD-013 | Structured evidence | undocumented |
FND-ACC-PRD-043 | medium | Pass 2 resolves the missing-brief portion: both requested briefs are present and have been read. The planning records still declare draft or proposed maturity, so this checkout does not establish a completed planning approval gate. Individual named Andrew decisions remain authoritative for the choices they cover. | MOD-ACC-PRD | Structured evidence | undocumented |
FND-ACC-PRD-044 | medium | A Platform template write commits outside Accounting's product transaction. Its success can survive a lost answer, failed response read or failed local commit. Accounting implements neither compensation nor durable reconciliation for these mismatches. | WF-ACC-PRD-001, ADR-ACC-PRD-008, STATE-ACC-PRD-004 | Structured evidence | debt |
FND-ACC-PRD-045 | medium | The draft overstated several table guarantees. Price overlap, active-kind admission, sellable revenue requirements and bundle-graph cycle checks rely on write validation rather than general database enforcement. Separate product locks do not serialize the whole graph, and a product-price reduction does not revalidate existing fixed shares. The final design states these limits. | DOM-ACC-PRD-001, DOM-ACC-PRD-002, DOM-ACC-PRD-004, ADR-ACC-PRD-005 | Structured evidence | debt |
FND-ACC-PRD-046 | medium | Migration and handover declarations assign realization to Commerce but do not establish its worker, delivery mechanism, retries, deadline or executable completion proof. The downstream transition stays unknown. No conclusion is drawn that every stored handover is still waiting. | STATE-ACC-PRD-005, WF-ACC-PRD-006, ADR-ACC-PRD-013 | Structured evidence | undocumented |
FND-ACC-PRD-047 | medium | The tax-default API supports inactive kinds, but the panel renders active kinds only. Console edit authority enables both assignment and clearing, although clearing requires backend delete authority; loading kinds additionally requires product read authority. These permission and coverage differences still need a decision and proof. | SCR-ACC-PRD-004, CAP-ACC-PRD-018 | Structured evidence | inconsistency |
FND-ACC-PRD-048 | medium | SQL replacement rejects an inactive kind while HTTP replacement does not repeat the creation-only activity check. With a readable Commerce register, SQL admits active and held audiences without a separate built-in exemption; denied register access bypasses audience validation. Existing parity descriptions and tests do not cover these variants. | WF-ACC-PRD-004, CAP-ACC-PRD-007, DOM-ACC-PRD-002 | Structured evidence | inconsistency |
FND-ACC-PRD-049 | low | No local Submissions publication or capture binding is declared. The external registry cannot be verified with the available repositories, so complete publication status and any architecture exemption remain unestablished. | SVC-ACC-PRD-products, ADR-ACC-PRD-014 | Structured evidence | undocumented |