Skip to content

Stakeholder questions (QD registry) ​

Numbers are never reused. A closed decision is never edited; open a new QD that supersedes it.

Status is Open, or Closed / Decided. The two closed words mean the same thing, that the question is answered (older entries say Closed, newer ones Decided); anything counting open questions counts only Open. A closed entry's status word is not rewritten to match.

QD-01 ​

  • Question: Which VAT scheme does each company use (standard, cash, flat rate)?
  • Stakeholder: Product Owner
  • Raised: 2026-09-27
  • Status: Closed
  • Decision: Both companies use standard accrual accounting. To be confirmed against Xero and HMRC once connected; a mismatch opens a new QD.
  • Decided by: Product Owner
  • Decided: 2026-09-27

QD-02 ​

  • Question: What yearly savings target should SM-2 carry?
  • Stakeholder: Product Owner
  • Raised: 2026-09-27
  • Status: Open

QD-03 ​

  • Question: What tolerance applies to the VAT control account cross-check in SPEC-001 S5?
  • Stakeholder: Product Owner
  • Raised: 2026-09-27
  • Status: Closed
  • Decision: No tolerance. The VAT control account cross-check must agree to the penny (0p); any difference blocks the draft and is shown in pence.
  • Decided by: Product Owner
  • Decided: 2026-09-28

QD-04 ​

  • Question: What evidence triggers the own-ledger horizon, and does the ledger live in this repo or in GetMy Books+?
  • Stakeholder: Product Owner
  • Raised: 2026-09-27
  • Status: Open

QD-05 ​

  • Question: When does the commit trailer hook move from warn-only to blocking? Proposed: after 2 weeks with no missing trailers.
  • Stakeholder: Product Owner
  • Raised: 2026-09-27
  • Status: Closed
  • Decision: Agreed. The hook becomes blocking after 2 weeks with no missing trailers, counted from 2026-09-28, so review on 2026-10-12. /sge:commit adds the trailer, which keeps the risk low.
  • Decided by: Product Owner
  • Decided: 2026-09-28

QD-06 ​

  • Question: FEAW is confirmed VAT-registered (QD-01), but a real-data sample of FEAW's live (non-voided/deleted) Xero sales invoices from 2025 onward shows every one coded TaxType: NONE — no output VAT at all. Bills do carry real codes (INPUT2, EXEMPTINPUT). Is NONE correct here (e.g. genuinely outside-the-scope-of-UK-VAT services to overseas clients) or a bookkeeping gap that has been under/over-stating VAT liability?
  • Stakeholder: Product Owner (with accountant input)
  • Raised: 2026-09-27
  • Status: Closed
  • Decision: A blanket NONE is wrong. FEAW has UK customers, whose sales are standard-rated (OUTPUT2, already used for AheadMG and WealthTechPros), and Australian business customers (FFS, Connection Capital, Professional Performance Portfolio Pty Ltd), whose services are outside the scope of UK VAT. Each sales line must carry a code that states its own treatment. Outside-scope sales still need a code that reaches the VAT return where HMRC requires it (Box 6), not "No VAT"; the accountant confirms that treatment and the Xero rate to use. The SPEC-001 mapping keeps blocking on NONE. Follow-ups are in QD-14.
  • Decided by: Product Owner
  • Decided: 2026-09-28
  • Why it matters: [[SPEC-001]]'s tax-type-to-box mapping (src/vat/tax-type-mapping.ts) deliberately blocks on NONE rather than guessing, precisely because of this ambiguity. Until resolved, any FEAW sales invoice coded NONE will block the VAT draft, naming the line (SPEC-001 S2) — this is intentional, not a bug.

QD-07 ​

  • Question: Which entities bank with Starling, and which Xero bank account is each Starling account linked to? Does WealthTechPros need setting up in the database first?
  • Stakeholder: Product Owner
  • Raised: 2026-09-28
  • Status: Closed
  • Decision: FEAW Services Ltd only. WealthTechPros is not in SPEC-003.
  • Decided by: Product Owner
  • Decided: 2026-09-28

QD-08 ​

  • Question: Will the accountant agree to switch on Xero's automatic bank reconciliation (JAX, beta, included on Comprehensive) for the Starling account? If yes, SPEC-003 also checks its work.
  • Stakeholder: Product Owner (with accountant input)
  • Raised: 2026-09-28
  • Status: Open

QD-09 ​

  • Question: What date window counts as a match between a Starling item and a Xero record in SPEC-003? Proposed: 0 days for card and bank payments, up to 5 days for invoice payments.
  • Stakeholder: Product Owner
  • Raised: 2026-09-28
  • Status: Closed
  • Decision: Same day for card and bank payments, up to 5 days for invoice payments. Starling timestamps are converted to the Europe/London date first, so late-night purchases fall on the right day. Anything outside the window is left unmatched, never guessed.
  • Decided by: Product Owner
  • Decided: 2026-09-28

QD-10 ​

  • Question: Does Starling's Xero feed include transfers to and from Spaces? Check one month of the Xero Reconcile tab against the Starling app.
  • Stakeholder: Product Owner
  • Raised: 2026-09-28
  • Status: Open

QD-11 ​

  • Question: Does SPEC-003 go before or after SPEC-001's exit test? CLAUDE.md allows one slice at a time, and SPEC-001 is current.
  • Stakeholder: Product Owner
  • Raised: 2026-09-28
  • Status: Closed
  • Decision: Before. SPEC-003 is implemented now, ahead of SPEC-001's exit test.
  • Decided by: Product Owner
  • Decided: 2026-09-28

QD-12 ​

  • Question: Finexer's answers: stable transaction ids across requests, months of history for Starling and Amex business accounts, pending versus settled, Startup plan price and what it includes, and what becoming their registered agent involves (checks, timeline, fees, insurance).
  • Stakeholder: Product Owner (with Finexer)
  • Raised: 2026-09-28
  • Status: Closed 2026-10-08 (Product Owner): no longer needed. GetMy Books reads statement files only and will not use Finexer (ADR 0035).

QD-13 ​

  • Question: Amex's CSV export dates a charge 1–2 days before Xero's Amex feed does (22 of 23 pairs 1 day apart on FEAW's August 2026 statement). Allow Amex statement lines to match Xero records up to 2 days apart, superseding QD-09's same-day rule for Amex only? Built that way pending this decision.
  • Stakeholder: Product Owner
  • Raised: 2026-09-28
  • Status: Closed
  • Decision: Yes. Amex statement lines may match Xero records up to 2 days apart, because Amex's dates cannot be relied on to line up with Xero's feed. This supersedes QD-09's same-day rule for Amex only; Starling keeps QD-09.
  • Decided by: Product Owner
  • Decided: 2026-09-28

QD-14 ​

  • Question: Follow-ups from QD-06. (a) What is FEAW's INV-0191 (to HMRC, 10 Dec 2025, £2,773.64, coded NONE)? It looks like a tax repayment entered as a sales invoice rather than a sale. (b) How did the VAT returns filed since January 2025 report the Australian-dollar sales coded NONE: in Box 6, or left off? (c) Which Xero tax rate should outside-scope sales use, so SPEC-001 can map it?

  • Stakeholder: Product Owner (with accountant input)

  • Raised: 2026-09-28

  • Status: Closed

  • Why it matters: (b) decides whether filed returns need correcting, and the SPEC-001 exit test (SM-3) compares drafts with filed returns. (c) blocks mapping those sales to a box.

  • Answer on (a), 2026-09-30 (Product Owner): INV-0191 is a tax refund from HMRC, not a sale. It stays off the VAT return. (b) and (c) stay open for the accountant.

  • Closed 2026-10-03 (Product Owner). (b) and (c) were not answered here: the accountant confirms them, tracked in docs/ROADMAP.md (QD-14 (b) and (c)) and needed before the SPEC-001 exit test.

QD-15 ​

  • Question: Starling dates a card payment when it is made and Xero's feed when it settles (M Dimsum: 26 vs 27 July 2026). Should Starling card payments get the same 2-day matching window as Amex (QD-13)? Same-day matching would show such a payment as missing from Xero, and bank_enter_missing_lines could then enter it a second time.
  • Stakeholder: Product Owner
  • Raised: 2026-09-28
  • Status: Closed
  • Decision: Yes. Starling card payments (source MASTER_CARD) match Xero records up to 2 days apart, the same as Amex. Starling bank transfers and direct debits keep QD-09's same-day rule. Supersedes QD-13's "Starling keeps QD-09" for card payments only.
  • Decided by: Product Owner
  • Decided: 2026-09-28

QD-16 ​

  • Question: Which VAT scheme does each company actually use? QD-01 said standard accrual for both, but FEAW's filed return for 1 Mar – 31 May 2026 is marked Cash · Quarterly · Late claims included in Xero. (a) Confirm FEAW is on cash accounting, and since when. (b) Which scheme is WealthTechPros on? (c) Should GetMy Books support cash accounting (issue #34, part 2), or stop with "unsupported scheme" as SPEC-001 S7 says today?

  • Stakeholder: Product Owner (Rob Duncan)

  • Raised: 2026-09-28

  • Status: Closed

  • Evidence so far: FEAW, filed return 1 Mar – 31 May 2026: Box 1 £4,290.14, Box 4 £1,059.53, Box 5 £3,230.61, Box 6 £21,450, Box 7 £5,408. The accrual draft for the same period gave Box 5 £5,127.91, so the scheme changes every box.

  • Why it matters: vat_prepare_return only derives standard accrual. Until this is settled and #34 is done, FEAW's returns must come from Xero, including the Jun–Aug 2026 return due 7 Oct 2026.

  • Decision on (c), 2026-09-29: Yes. GetMy Books supports cash accounting, and checks filed returns against Xero (SPEC-001 S9, S10; issue #34). Decided by the Product Owner. (a) and (b) stay open for Rob Duncan.

  • Answer on (a) and (b), 2026-09-30 (Product Owner): (a) FEAW has been on cash accounting for a long time; the exact start date wasn't given, and nothing depends on it now. (b) WealthTechPros isn't VAT-registered yet (see QD-17 (a)), so it has no scheme. Closed.

QD-17 ​

  • Question: Which further obligations apply, for SPEC-004's deadline radar? (a) Is WealthTechPros VAT-registered, and if so, which months do its VAT quarters end in? (b) Does either company run payroll (monthly PAYE/RTI deadlines)? (c) Do the directors want Self Assessment dates too?

  • Stakeholder: Product Owner

  • Raised: 2026-09-29

  • Status: Closed

  • Why it matters: Until answered, SPEC-004 covers Companies House, FEAW's VAT and both companies' Corporation Tax only.

  • Answer on (a) and (b), 2026-09-30 (Product Owner): (a) WealthTechPros is not VAT-registered today but will be; nothing is built for its VAT until it registers, and its quarter months are asked then. (b) FEAW runs payroll, so PAYE and RTI deadlines apply to FEAW. WealthTechPros has no employees; its owners take profit shares as dividends (it is a limited company, 14111544). (c) stays post-MVP.

  • Closed 2026-10-03 (Product Owner). All parts are answered above.

QD-18 ​

  • Question: Approve ADR 0021: SPEC-006 may mark sales invoices and bills paid in Xero from chat, only through preview then confirm by ID (M4), audited, never above the amount due, and never moving money?
  • Stakeholder: Product Owner
  • Raised: 2026-09-29
  • Status: Decided
  • Recommended: Yes.
  • Decision, 2026-09-30: Yes: invoices and bills can be marked paid from chat, through preview then confirm (ADR 0021 accepted). Approved by the Product Owner ("approve all recommendations").

QD-19 ​

  • Question: Should SPEC-006 email customers to chase overdue invoices, or only give the owner a chase list?
  • Stakeholder: Product Owner
  • Raised: 2026-09-29
  • Status: Decided
  • Recommended: Chase list only in v1. Emailing customers is outward-facing, in the company's name, and needs its own approval flow.
  • Decision, 2026-09-30: Chase list only: SPEC-006 drafts messages for the owner to send and never contacts customers. Approved by the Product Owner ("approve all recommendations").

QD-20 ​

  • Question: Approve ADR 0022 (attaching evidence to Xero records is in scope; receipt capture stays out), and how files arrive: a local allowed folder for stdio, plus a web upload page behind Access for claude.ai?
  • Stakeholder: Product Owner
  • Raised: 2026-09-29
  • Status: Decided
  • Recommended: Yes to both. Build the local folder first; the web upload page follows the data protection ADR.
  • Decision, 2026-09-30: Yes to both (ADR 0022 accepted): the local folder first; the web upload page after the data protection ADR. Approved by the Product Owner ("approve all recommendations").
  • Superseded, 2026-10-01: how files arrive is now QD-27 (ADR 0031). ADR 0022 itself stands.

QD-21 ​

  • Question: How should reminder emails be sent?
  • Stakeholder: Product Owner
  • Raised: 2026-09-29
  • Status: Decided
  • Recommended: Microsoft Graph sendMail from a dedicated notifications@getmy.group mailbox, with Mail.Send limited to that mailbox by an application access policy (docs/plans/email-reminders.md).
  • Decision, 2026-09-30: Microsoft Graph sendMail from notifications@getmy.group, limited to that one mailbox: RBAC for Applications in Exchange Online, or an application access policy if that isn't available (docs/plans/email-reminders.md). Approved by the Product Owner ("approve all recommendations").

QD-22 ​

  • Question: Who receives deadline reminders, and at which thresholds?
  • Stakeholder: Product Owner
  • Raised: 2026-09-29
  • Status: Decided
  • Recommended: Everyone with access to the company (today Rob and Fraser for FEAW). 30, 14, 7 and 3 days before, on the day, then weekly while overdue; one email per person per day.
  • Decision, 2026-09-30: Everyone with access to the company; 30, 14, 7 and 3 days before, on the day, then weekly while overdue; one email per person per day. Approved by the Product Owner ("approve all recommendations").

QD-23 ​

  • Question: Start the HMRC developer application now (sandbox, then production credentials for MTD VAT read:vat), given HMRC's approval lead time?
  • Stakeholder: Product Owner
  • Raised: 2026-09-29
  • Status: Decided
  • Recommended: Yes. The paperwork runs in parallel with SPEC-006; nothing is built until its slice.
  • Decision, 2026-11-04: Parked with issue #85, which closes as parked: the HMRC connection is not built while ADR 0036 stands (GetMy Books does not file), and docs/plans/hmrc-connection.md keeps the plan. Nothing is applied for or built; a new QD reopens this only if ADR 0036 is amended.
  • Decided by: Product Owner
  • Decided: 2026-11-04

QD-24 ​

  • Question: Bank lines that match a Xero record on amount but are dated further apart than the windows allow (FEAW Amex, £439.16, 8 days apart): widen the window, or suggest them as possible matches?
  • Stakeholder: Product Owner
  • Raised: 2026-09-29
  • Status: Decided
  • Recommended: Keep the windows (QD-09, QD-13, QD-15). Add a "possible match, check it" list for exact-amount pairs up to 10 days apart, never auto-matched or entered (issue #45).
  • Decision, 2026-09-30: Keep the windows, and add a "possible match, check it" list for exact-amount pairs up to 10 days apart, never auto-matched or entered (issue #45). Approved by the Product Owner ("approve all recommendations").
  • Amended, 2026-11-04 (#328, Product Owner): a possible match is still never auto-matched or entered on a guess, but the owner may release one after checking it in Xero, by naming every record listed; a record entered after the preview still stops it at Approve. SPEC-003 S77 and S79.

QD-25 ​

  • Question: HMRC issues MTD VAT production credentials only to software that can submit a return, after a live submission. How does GetMy Books get production read access?
  • Stakeholder: Product Owner
  • Raised: 2026-09-30
  • Status: Decided
  • Recommended: Email HMRC's SDS team now asking for read:vat only for in-house use by our two companies; build and test in the sandbox meanwhile. Only if HMRC refuses, build SPEC-002 filing and file one real FEAW return through GetMy Books (Sep–Nov 2026, due 7 Jan 2027), with Rob and the accountant agreeing. See docs/plans/hmrc-connection.md.
  • Decision, 2026-11-04: Parked with issue #85, which closes as parked: the HMRC connection is not built while ADR 0036 stands (GetMy Books does not file), and docs/plans/hmrc-connection.md keeps the plan. Nothing is applied for or built; a new QD reopens this only if ADR 0036 is amended.
  • Decided by: Product Owner
  • Decided: 2026-11-04

QD-26 ​

  • Question: Whose Government Gateway user ID authorises GetMy Books to read FEAW's VAT account (and later WealthTechPros')?
  • Stakeholder: Rob
  • Raised: 2026-09-30
  • Status: Decided
  • Recommended: Whoever signs in to FEAW's VAT online account today, Rob or the accountant, to confirm. It must be the business's own sign-in, not an agent's.
  • Decision, 2026-11-04: Parked with issue #85, which closes as parked: the HMRC connection is not built while ADR 0036 stands (GetMy Books does not file), and docs/plans/hmrc-connection.md keeps the plan. Nothing is applied for or built; a new QD reopens this only if ADR 0036 is amended.
  • Decided by: Product Owner
  • Decided: 2026-11-04

QD-27 ​

  • Question: How do receipts reach GetMy Books for SPEC-005, now that Rob uses the claude.ai connector and keeps receipts in Gmail (#120)?
  • Stakeholder: Product Owner
  • Raised: 2026-10-01
  • Status: Decided
  • Recommended: Forward them to the organisation's Xero Files inbox. GetMy Books lists the inbox and links each file to its record, never holding the file. Rejected: the model passing file bytes (token cost, corruption), reading Gmail or Outlook directly (a grant per user, Google's 7-day expiry for unverified apps, a burden on accountants), and an upload page (download, then upload again). Fallback: our own Cloudflare Email Worker address.
  • Decision, 2026-10-01: Xero Files inbox (ADR 0031). Product Owner: "the email forwarding to the Xero inbox is the perfect solution, let's go for that". The local folder and upload page are dropped.

QD-28 ​

  • Question: SPEC-005 follow-ups: should finding a record use the card that paid; what happens to a receipt the company did not pay; may Claude forward receipts from the owner's mailbox; and can "reconcile my Amex" use the receipts in the inbox?
  • Stakeholder: Product Owner
  • Raised: 2026-10-01
  • Status: Decided
  • Recommended: (1) Filter candidate records by the card that paid, matched to the company's Xero accounts; say "unknown" rather than guess. (2) Move a receipt the company did not pay, after Approve, to a Xero Files folder "Not <entity>"; never delete it. (3) A tool returns the company's Xero inbox address to the signed-in owner, so Claude can forward receipts with the owner's own mail connector (Microsoft 365 or Gmail); GetMy Books still reads no mailbox (ADR 0031, amended). (4) A prompt "forward my receipts to Xero" that shows the owner the list before sending anything. (5) "Reconcile my Amex" also uses the receipts in the inbox: one read of the bank lines and records, an action per receipt, and one approval card for all the attachments.
  • Decision, 2026-10-01: As recommended, all five. Product Owner: "yeah 'Not FEAW' inbox is good" and "yes do that". ADR 0031 amended; SPEC-005 S10 to S23.
  • Withdrawn, 2026-10-01: Decision 2 (the "Not <entity>" folder). Xero's Documents (the renamed Files) does not show folder moves made through the Files API: the folder stayed empty and the files stayed in the Documents Inbox. The Product Owner agreed to drop set-aside; the owner archives such receipts in Xero Documents. ADR 0031 amended again; SPEC-005 S13 to S16 removed.

QD-29 ​

  • Question: ADR 0032 lets statement text be passed inline in a tool call, held in memory only, so statement-file banks work from the deployed server. ADR 0015 point 3 treats statement files as the account holder reading their own accounts, not a service to others. Is a customer sending us their own statement text for their own reconciliation outside an Account Information Service under the Payment Services Regulations 2017, or does it need the aggregator route (and Finexer's agent status) like any other bank read for another business?
  • Stakeholder: Product Owner (with advice if needed)
  • Raised: 2026-10-03
  • Status: Decided
  • Recommended: Offer the inline fallback to the owner's own companies only (FEAW, WealthTechPros) until this is answered. Customers use the aggregator route.
  • Decision, 2026-10-03: Not a service to others: it is the person's own files. Product Owner: "that is not a service to others - it is the person's own files". The inline route is open to any customer's own statements, with no per-entity switch (ADR 0032 Decision 2, SPEC-003 scope; S27 and the inline_statements_enabled column dropped). No legal advice is recorded; revisit if the service ever fetched bank data itself, which is the aggregator route (ADR 0015).

QD-30 ​

  • Question: Supersedes QD-01. Which VAT scheme does each company use?
  • Stakeholder: Product Owner
  • Raised: 2026-10-03
  • Status: Closed
  • Decision: FEAW uses the cash accounting scheme, not standard accrual as QD-01 said. Its filed VAT return for 1 Mar to 31 May 2026 (filed 23 Jun 2026) is marked Cash in Xero, and the Product Owner confirmed on 2026-09-30 that FEAW has been on cash accounting for a long time (QD-16 (a)). WealthTechPros is not VAT-registered yet, so it has no scheme (QD-16 (b), QD-17 (a)).
  • Decided by: Product Owner
  • Decided: 2026-09-30 (recorded 2026-10-03)
  • Supersedes: QD-01. QD-01 was corrected in place on 2026-09-28, against this registry's rule; its original text is restored and this QD records the correction.
  • See: QD-16, issue #34.

QD-31 ​

  • Question: For "reconcile my Amex" to work in Claude on the web, desktop or phone, bank_entries_preview must take inline statement text (SPEC-003 S36). The stored preview would then hold each chosen line's date, amount, direction and counterparty until it is confirmed or expires (15 minutes). ADR 0032 says statement text is never stored. Is keeping only the fields Xero is sent, for the life of the preview, acceptable?
  • Stakeholder: Product Owner
  • Raised: 2026-10-05
  • Status: Decided
  • Recommended: Yes. Those fields go into Xero on confirm anyway; nothing else from the text is kept, and the preview row is deleted when it ends. Record it as an amendment to ADR 0032.
  • Decision, 2026-10-05: Yes. The preview keeps only the fields sent to Xero, until it is confirmed or expires. Product Owner: "31 yes". Amend ADR 0032 when S36 is built.
  • See: SPEC-003 S34 to S36, ADR 0032.

QD-32 ​

  • Question: vat_corrections_preview corrects only records the check flagged (ADR 0017, SPEC-003 S16). On 2026-10-05 the Product Owner recoded about 30 lines by hand in Xero (Anthropic to reverse charge, Amex fees to exempt, personal items to No VAT) because none were flagged. Should the owner be able to name any reconciled record, with a reason, for the same preview-and-Approve correction?
  • Stakeholder: Product Owner
  • Raised: 2026-10-05
  • Status: Decided
  • Recommended: Yes, with the reason logged and the same guards (approval card, HMRC error limit, once per record).
  • Decision, 2026-10-05: Yes, with the reason logged and the same guards. Product Owner: "32 yes".
  • See: SPEC-003 S37, ADR 0017.

QD-33 ​

  • Question: For the Companies House confirmation statement (SPEC-009), does GetMy Books only prepare it (the owner files on Companies House's own service, £50), or does it also submit it through Companies House software filing after approval on the web page?
  • Stakeholder: Product Owner
  • Raised: 2026-10-05
  • Status: Decided
  • Recommended: Prepare only for now. Submitting needs a Companies House presenter account and software filing credentials, and CLAUDE.md rule 5 keeps filing out of MCP tools. Revisit once SPEC-002's approval page exists.
  • Decision, 2026-10-05: Prepare only. The owner files on Companies House's own service. Product Owner: "33 prepare only".
  • See: SPEC-009.

QD-34 ​

  • Question: In the September Amex exit test (2026-10-06), Claude re-typed two attached CSVs into bank_entries_preview, garbled some rows, and the call timed out. May the server keep the lines bank_reconciliation_check read from statement text in memory for a short time, so the preview can refer to them by ID?
  • Stakeholder: Product Owner
  • Raised: 2026-10-06
  • Status: Decided
  • Decision, 2026-10-06: Yes. In server memory only, keyed by person, company, account and period, for at most 15 minutes, never written to the database or logs (Product Owner: "yes, raise these as issues and build them with slice 5 today"). ADR 0032 gets a dated amendment. SPEC-003 S39, #194.
  • See: ADR 0032, QD-31, SPEC-003 S36 and S39.

QD-35 ​

  • Question: The activity log (SPEC-010, ADR 0033) keeps what Claude proposed, who approved or declined it, and what Xero then held. How long is it kept, and how are old rows removed?
  • Stakeholder: Product Owner
  • Raised: 2026-10-06
  • Status: Decided
  • Recommended: 6 years from the end of the financial year a row relates to, the same as ledger_write and HMRC record keeping (ADR 0026, "Proposed retention"), removed by a scheduled delete run by the owner role, with a test. Until then nothing deletes a row.
  • Decided-pending-PO, 2026-11-03: folded into the ADR 0026 amendment of 2026-11-03 (issue #295): while a customer, 6 years from the end of the financial year of the row (company profile year end, else 7 years from the row), the same as ledger_write; when the company stops being a customer, deleted with it 90 days later, as the published privacy notice and data processing agreement say. The six-year delete runs (delete_old_activity_log(), migration 0034); the company delete (delete_retired_entities()) is held. Open for the Product Owner to confirm and close.
  • Decided 2026-11-04 by the Product Owner (chat), PR #360: (A) a company is deleted 90 days after it leaves, as DPA section 9 says; (B) it leaves at the later of its subscription ending and its Xero connection going; (C) a comped company never leaves; (D) the Xero connection is gone when there is no connection row or its token has not been refreshed or saved for 60 days; (E) ledger_write and activity_log rows are deleted, not anonymised, 6 years after the end of their financial year while a customer, and with the company when it is deleted; (F) the clock starts at deploy: no company is deleted until 90 days after the deploy that switches the company deletes on, whatever its history. The company and person deletes run on the sweep.
  • Size: a row is a few KB (detail capped at 64 KB); at tens of previews a month the table stays in the megabytes for years, so retention is a records question, not a space one.
  • See: SPEC-010, ADR 0033, ADR 0026.
  • Decided by: Product Owner (chat, 2026-11-04)
  • Decided: 2026-11-04

QD-36 ​

  • Question: SPEC-012: what amount makes a purchase look like a capital item (the threshold), and is it one figure per company or by asset type?
  • Stakeholder: Product Owner, Rob (FEAW)
  • Raised: 2026-10-08
  • Status: Closed
  • Decision: Capitalisation threshold is £500, one figure per company, a flag level only (a flag is not a ruling). Rob to confirm if he disagrees.
  • Decided by: Product Owner
  • Decided: 2026-10-08
  • See: SPEC-012 S4, S5.

QD-37 ​

  • Question: SPEC-012 needs the new Xero scopes assets.read and accounting.reports.balancesheet.read (and a reconnect per company). Approve, and do it in the same reconnect as the management reporting scopes?
  • Stakeholder: Product Owner
  • Raised: 2026-10-08
  • Status: Closed
  • Decision: Approved. Add assets.read and the balance sheet report scope (accounting.reports.balancesheet.read); one reconnect per company, together with the other pending scopes. Exact names to be checked in the Xero developer portal before build.
  • Decided by: Product Owner
  • Decided: 2026-10-08
  • See: SPEC-012 integration sketch, docs/plans/management-reporting.md.

QD-38 ​

  • Question: What depreciation policy should "depreciation run for the period" be judged against (monthly or yearly run, rates, which asset types), and which ledger accounts are the fixed asset, accumulated depreciation and expense accounts for each company?
  • Stakeholder: Rob (FEAW)
  • Raised: 2026-10-08
  • Status: Closed
  • Decision: GetMy Books reads each company's asset types, depreciation method and rate, and the asset, accumulated depreciation and expense accounts from Xero's fixed asset settings via the Assets API. If none are set up, it says so and asks the owner or accountant. No manual policy entry.
  • Decided by: Product Owner
  • Decided: 2026-10-08
  • See: SPEC-012 S3, S8.

QD-39 ​

  • Question: Can GetMy Books get Xero Finance API access to read unreconciled bank statement lines (SPEC-013 slice c)? The standard Accounting API does not expose them.
  • Stakeholder: Product Owner
  • Raised: 2026-10-08
  • Status: Closed
  • Decision: Approved. The Product Owner will apply to Xero for Finance API access (owner action; steps in SPEC-013). SPEC-013 slice (c) stays blocked until access is granted.
  • Decided by: Product Owner
  • Decided: 2026-10-08
  • See: SPEC-013, ADR 0015, ADR 0024, ADR 0034.

QD-40 ​

  • Question: Which statement formats and which banks must slice (a) cover first? Proposed: CSV and OFX only, with FEAW's Starling and Amex files and WealthTechPros' bank as the test set.
  • Stakeholder: Product Owner
  • Raised: 2026-10-08
  • Status: Closed
  • Decision: Slice (a) covers OFX and QIF as standard readers first, then CSV presets for Barclays, HSBC, Lloyds, NatWest/RBS, Santander, Revolut Business (WealthTechPros' bank), Tide, Monzo Business, Starling, Wise and Amex (Amex moves onto the generic reader), plus a saved per-account column mapping for anything else. PDF excluded.
  • Decided by: Product Owner
  • Decided: 2026-10-08
  • See: SPEC-013 slice (a).

QD-41 ​

  • Question: Keep the Starling API as an optional live source (slice b) for FEAW, or move FEAW to statement files too?
  • Stakeholder: Product Owner
  • Raised: 2026-10-08
  • Status: Closed
  • Decision: Keep Starling as a live source behind the bank-source interface.
  • Decided by: Product Owner
  • Decided: 2026-10-08
  • Superseded (Product Owner, 2026-10-08): FEAW moves to Starling statement files. GetMy Books must not access any bank account itself. Once Get My Books Ltd serves FEAW as a customer, a token on FEAW's account would be access to a payment account (PSRs 2017 reg 2; PERG 15.3 Q25A). The stored token was cleared on 2026-10-08. The Starling source code stays but is not used.
  • See: SPEC-013 slice (b), ADR 0034, ADR 0015.

QD-42 ​

  • Question: May GetMy Books save a per-account column mapping (column names and formats only, no statement content), and is ADR 0034 approved?
  • Stakeholder: Product Owner
  • Raised: 2026-10-08
  • Status: Closed
  • Decision: Yes: a per-account column mapping (names and formats only, no statement content) may be saved. ADR 0034 accepted (2026-10-08).
  • Decided by: Product Owner
  • Decided: 2026-10-08
  • See: SPEC-013 S1, S8, ADR 0034.

QD-43 ​

  • Question: SPEC-014's complete mode reads Xero's Journals endpoint (accounting.journals.read). ADR 0024 records that Xero grants this scope only to apps on its Advanced developer tier after a security assessment. Does the GetMy Books Xero app's tier include it (and is it worth applying for)?
  • Stakeholder: Product Owner
  • Raised: 2026-10-08
  • Status: Decided
  • Interim: The scope is not requested by default, since asking for one the app may not have could break every connect. account_history works without it from invoices, bills, credit notes, bank transactions, payments and manual journals, and says what it cannot see. XERO_JOURNALS_SCOPE=on adds the scope once the tier allows it; each company then reconnects.
  • See: SPEC-014 integration sketch, ADR 0024, README.
  • Decision, 2026-11-04: Do not apply for Xero's Advanced tier now. The interim stands: accounting.journals.read is not requested by default, account_history works from the other records and says what it cannot see, and XERO_JOURNALS_SCOPE=on stays the switch if the tier is granted later.
  • Decided by: Product Owner
  • Decided: 2026-11-04

QD-44 ​

  • Question: Should one subscription cover every company one owner connects (per-owner licence) instead of £19.99 per company?
  • Stakeholder: Product Owner
  • Raised: 2026-10-30
  • Status: Decided
  • Recommended: Keep per-company pricing for customers (ADR 0037 decision 1 and 2; SPEC-016 "no seats or more than one price"); the owners' own companies are comped (migrations 0016 and 0024, ADR 0037 amended 2026-10-30). A per-owner plan is new scope: a principal-level subscription (principal_subscription keyed by principal, with a principal-scoped RLS policy and a security definer recorder keyed by the subscription's principal_id metadata), Checkout with a quantity, a Stripe quantity change (prorated subscriptionItems.update) when a company is added or removed, including on company and account deletion, and an entitlement covering relation (which principal's plan pays for a company, since entity_access is many-to-many) read by readLicence/isEntitled, with the owners' view, revenue and the home card counting a plan once. It needs an amendment to ADR 0037 and SPEC-016 before any code.
  • See: issue #310, ADR 0037 (amended 2026-10-30), SPEC-016 S14, SPEC-018 out of scope.
  • Decision, 2026-11-04: Keep per-company pricing for customers; the owners' own companies stay comped (migrations 0016 and 0024, ADR 0037 amended 2026-10-30). No per-owner plan is built (issue #310).
  • Decided by: Product Owner
  • Decided: 2026-11-04

QD-45 ​

  • Question: Which sales account does a recharge use? FEAW has no "Recharged expenses" account; invoice_create_preview (SPEC-019) takes the account code the owner gives and never picks one.
  • Stakeholder: Product Owner
  • Raised: 2026-10-30
  • Status: Decided
  • Recommended: The owner adds a revenue account in Xero (e.g. "Recharged expenses") and names it on each recharge; the tool never picks one.
  • See: SPEC-019, ADR 0043, issue #308.
  • Decision, 2026-11-04: As recommended: the owner adds a revenue account in Xero (for example "Recharged expenses") and names it on each recharge; invoice_create_preview never picks one.
  • Decided by: Product Owner
  • Decided: 2026-11-04

QD-46 ​

  • Question: How is a bill a director paid personally settled, per company: reimbursement from the bank account, a Directors' Loan Account journal, or an expense claims account? SPEC-019 S17 leaves such a bill awaiting payment.
  • Stakeholder: Product Owner
  • Raised: 2026-10-30
  • Status: Decided
  • Recommended: Ask Rob and the accountant per company; until decided the bill is left awaiting payment and nothing about settlement is written.
  • See: SPEC-019 S17, ADR 0043 decision 8, issue #306.
  • Decision, 2026-11-04: A bill a director paid personally is settled by a Xero payment from the company's Directors' Loan Account, shown in the approval card and approved there by the owner. The account is read from the company's chart of accounts by name and type and named on each card; 835 is only Xero's UK default code and is never assumed. If the chart has no such account, or more than one, the settlement is refused. It goes live for both companies now (issue #335). The accountant is asked to confirm the treatment for FEAW and WealthTechPros before the owner uses it on a real bill; that is advice to the owner, not a gate in the code. Unpaid Expense Claims is not offered.
  • Decided by: Product Owner (chat, 2026-11-04)
  • Decided: 2026-11-04

QD-47 ​

  • Question: Who may send to a company's receipts address?
  • Stakeholder: Product Owner
  • Raised: 2026-10-30
  • Status: Decided
  • Recommended: Any sender; the reply tells them; the owner rotates the address if misused.
  • See: SPEC-021, ADR 0044, issue #304.
  • Decision, 2026-11-04: As recommended: any sender may send to a company's receipts address; the reply tells them what happened; the owner rotates the address if it is misused.
  • Decided by: Product Owner
  • Decided: 2026-11-04

QD-48 ​

  • Question: QD-17 (a) said nothing is built for WealthTechPros' VAT until it registers. WEALTH TECH PROFESSIONALS LIMITED is now registering: should GetMy Books keep its lines at No VAT and log the VAT each receipt shows, so its first return can reclaim pre-registration VAT (HMRC VAT Notice 700, section 11)?
  • Stakeholder: Product Owner
  • Raised: 2026-10-30
  • Status: Decided
  • Recommended: Build SPEC-020 now, so the first return's reclaim is traceable to the lines and receipts it rests on: a VAT registration status and date in the company profile, only No VAT accepted while not registered or registering, and a pre-registration log with the HMRC rule worked out by code. This reopens QD-17 (a)'s "nothing is built for its VAT until it registers" for this company only.
  • See: SPEC-020, issue #307, QD-17 (a), QD-16 (b).
  • Decision, 2026-11-04: Yes: SPEC-020 is built and live (PR #337). QD-17 (a)'s "nothing is built for its VAT until it registers" is reopened for WEALTH TECH PROFESSIONALS LIMITED only.
  • Decided by: Product Owner
  • Decided: 2026-11-04

QD-49 ​

  • Question: Does a read-only table or chart of books data, rendered inside Claude by an MCP Apps view from a tool's structuredContent (for example a sortable aged-debtors table beside payments_aged's summary), count as "Claude is the interface", or as the dashboard of the books that docs/not-doing.md rules out?
  • Stakeholder: Product Owner
  • Raised: 2026-11-02
  • Status: Decided
  • Recommended: Allow read-only MCP Apps views that render only the code-built structuredContent the tool already returns (built in src/present/ from src/rules/ and src/vat/): no figure, total, rounding or conversion of their own, no button that calls a writing tool, nothing in them is approval, no outside script, style, font or image, the bundle inlined and pinned as the approval card's is, and the text summary kept as the base reply for Claude Code and any client without MCP Apps. Pilot on payments_aged, with a refactor-guard HTML test and a fake-host test as the approval card has, and an exit test by the Product Owner in Claude Desktop and on claude.ai: the table's figures match the text summary one for one. The not-doing row keeps its words and cites ADR 0045. If refused, the row stands, ADR 0045 records the "no", and issue #99 closes with no pilot.
  • Decision, 2026-11-04: Allowed, as recommended. Read-only MCP Apps views that render only the code-built structuredContent the tool already returns are "Claude is the interface", not the dashboard docs/not-doing.md rules out, within ADR 0045's limits; the pilot is payments_aged (SPEC-006 S19) and the Product Owner's exit test in Claude Desktop and on claude.ai is still to run. Product Owner, in chat: QD-49 answered with the recommended option.
  • Decided by: Product Owner
  • See: ADR 0045 (accepted 2026-11-04), issue #99, ADR 0005, ADR 0041, docs/plans/human-confirmation-for-writes.md (the approval card, decided 2026-10-01), SPEC-006 slice 1.

QD-50 ​

  • Question: The #326 fix makes deleting an account set each subscription to end at the end of the paid period instead of cancelling it at once. Terms 3.3 and the Privacy notice say "at once", and terms 9.1 promises at least 30 days' notice by email of a change. Ship the new wording and a new TERMS_VERSION with the code, or later?
  • Stakeholder: Product Owner
  • Raised: 2026-11-04
  • Status: Decided
  • Decision, 2026-11-04: Ship the #326 code now with TERMS_VERSION and the legal documents unchanged; the code's behaviour is more favourable to the customer than the published wording. The owner emails notice of the new 3.3 and Privacy notice wording to every account holder; the wording and TERMS_VERSION (2026-12-04.1) change on 4 December 2026, in their own pull request. Product Owner, in chat.
  • Decided by: Product Owner (chat, 2026-11-04)
  • Decided: 2026-11-04
  • See: SPEC-016 S20, issue #326, PR #346, PR #366, terms 9.1.