Skip to content

Latest commit

 

History

History
35 lines (21 loc) · 1.66 KB

File metadata and controls

35 lines (21 loc) · 1.66 KB

Product

Register

product

Users

Accountants and chartered-accountancy teams using Tally on a desktop during day-to-day receivables and payables work. They need to see which parties carry the largest exposure and how old the underlying bills are without first interpreting Bridge's sync machinery.

Product Purpose

For Unit A, Bridge reads one verified Tally company and presents an in-memory outstandings view: receivable and payable totals, four ageing buckets, top parties, oldest-bill age, and a clear freshness line. Success means the numbers are correct, locally computed from vouchers and bill allocations, and visibly tied to a complete or explicitly partial live read.

Brand Personality

Trustworthy, restrained, evidence-led.

Anti-references

  • A generic SaaS dashboard made from interchangeable metric cards.
  • A technical capability passport, sync diagram, or evidence matrix competing with the business result.
  • Decorative finance styling, unexplained color, or animation that makes the numbers feel less auditable.

Design Principles

  • Lead with the accountant's business question, not Bridge's implementation.
  • Make freshness and incomplete-read states impossible to miss.
  • Use familiar accounting labels and Indian-number formatting.
  • Keep the first screen focused: no filters, drill-down, or configurability in Unit A.
  • Prefer dense, legible comparison over decorative containers.

Accessibility & Inclusion

Target WCAG 2.1 AA contrast and keyboard operation. Never communicate receivable/payable or complete/partial state by color alone. Respect reduced-motion preferences and keep all financial values readable at desktop and narrow-window widths.