Repository Docs & Knowledge Base

Consolidated Spensara documentation repository (722 Markdown & architecture documents in ../repository)

Built Word Documents (.docx): Spensara Overview (.docx) Capability Assessment (.docx) Brink POS Ingestion Analysis (.docx) The Borg Ingestion Architecture (.docx)

Warehouse Model (93)

Analytical data warehouse schemas, curated tables, and Redshift/Athena data models.

warehouse-model/docs/features/ETL/warehouse-data/curated-model/pos_tenders.md 4,938 bytes · Updated Oct 23, 2026 10:44 AM EDT

Raw File

curated.pos_tenders

Purpose

This table stores tender master configuration from the POS. It defines how payment methods behave operationally, how they print, validate, authorize, round, and interact with drawers or processors.

It is primarily reference data used to interpret transaction tenders rather than a transactional fact table.

Schema contract

The deployed SQL under backend/Kds.Ai.Warehouse/Sql/Bootstrap/Tenant/Curated/ is the source of truth for the current column names, types, and nullability.

Column groups

Business properties describe the business entity, event, fact, or reference record represented by the table.
Technical and ETL properties describe warehouse lineage, surrogate keys, source reconciliation, tenant scoping, slowly changing dimension controls, and ingestion metadata.

Business properties

Column	Type	Nullable	Business Meaning
`id`	`INTEGER`	Yes	Tender identifier in the POS source.
`usernumber`	`INTEGER`	Yes	User-visible tender number in the POS.
`name`	`VARCHAR(10)`	Yes	Short tender name shown to operators.
`cash`	`VARCHAR(1)`	Yes	Flag indicating whether this tender behaves as cash.
`gcert`	`VARCHAR(1)`	Yes	Flag indicating gift certificate support.
`change`	`VARCHAR(1)`	Yes	Flag indicating whether this tender can issue change.
`reportas`	`INTEGER`	Yes	Reporting classification code for the tender.
`house`	`VARCHAR(1)`	Yes	Flag indicating house-account behavior.
`active`	`VARCHAR(1)`	Yes	Flag indicating whether the tender is active.
`tips`	`VARCHAR(1)`	Yes	Flag indicating whether the tender supports tips.
`cardtype`	`INTEGER`	Yes	Card type classification code.
`fcurrncyid`	`INTEGER`	Yes	Foreign currency identifier.
`accntrcvbl`	`VARCHAR(1)`	Yes	Flag indicating accounts-receivable behavior.
`cashcard`	`VARCHAR(1)`	Yes	Flag indicating cash-card behavior.
`ischeck`	`VARCHAR(1)`	Yes	Flag indicating check tender behavior.
`external`	`VARCHAR(1)`	Yes	Flag indicating external processor or external payment behavior.
`debit`	`VARCHAR(1)`	Yes	Flag indicating debit-card behavior.
`giftcard`	`VARCHAR(1)`	Yes	Flag indicating gift-card behavior.
`iscredtcrd`	`VARCHAR(1)`	Yes	Flag indicating credit-card behavior.
`roundactiv`	`VARCHAR(1)`	Yes	Flag enabling rounding for this tender.
`roundto`	`DOUBLE PRECISION`	Yes	Rounding increment.
`roundmthd`	`INTEGER`	Yes	Rounding method code.
`ebt`	`VARCHAR(1)`	Yes	Flag indicating EBT behavior.
`ebttype`	`INTEGER`	Yes	EBT subtype code.
`tdrsurch`	`INTEGER`	Yes	Tender surcharge identifier.
`disloyalty`	`VARCHAR(1)`	Yes	Flag disabling loyalty behavior for this tender.
`iscampus`	`VARCHAR(1)`	Yes	Flag indicating campus-payment behavior.
`payment_family`	`VARCHAR(100)`	Yes	Standardized payment family code such as cash, card, wallet, loyalty, or house account.
`payment_family_name`	`VARCHAR(255)`	Yes	Readable business name of the standardized payment family.
`is_digital`	`BOOLEAN`	Yes	Canonical flag indicating whether the tender is a digital payment method.
`is_cash_equivalent`	`BOOLEAN`	Yes	Canonical flag indicating whether the tender behaves like cash in analysis.
`processor_name`	`VARCHAR(255)`	Yes	Readable payment processor or external provider name when available.

Technical and ETL properties

Column	Type	Nullable	Technical Meaning	Notes
`tender_key`	`BIGINT`	Yes	Stable warehouse key for the tender entity.
`source_system`	`VARCHAR(100)`	Yes	Canonical name of the source platform that produced the tender row.
`source_tender_id`	`VARCHAR(199)`	Yes	Original tender identifier from the source platform.
`tenant_key`	`BIGINT`	Yes	Stable warehouse key for the tenant, brand, or client that owns the tender configuration.
`tenant_name`	`VARCHAR(255)`	Yes	Readable tenant, brand, or client name associated with the tender.
`effective_from_utc`	`TIMESTAMP`	Yes	UTC timestamp from which the current tender version is valid.
`effective_to_utc`	`TIMESTAMP`	Yes	UTC timestamp until which the current tender version is valid.
`is_current`	`BOOLEAN`	Yes	Canonical flag indicating whether the row is the current tender version.
`_etl_batch_id`	`VARCHAR(256)`	Yes	ETL batch lineage identifier.
`_etl_source_type`	`VARCHAR(100)`	Yes	Source adapter type used by ETL.
`_etl_ingested_at`	`TIMESTAMP`	No	Warehouse ingestion timestamp for the curated row.	Required ingestion audit timestamp.