A dashboard does not fix broken data

Many companies ask for a dashboard when they really have an integration problem. They want margin, cash flow, sales by branch, and receivables, but those data points live in systems that do not talk to each other.

A beautiful chart over incomplete data only makes the error look executive.

For Dominican companies, the opportunity is connecting four sources: POS, e-CF, bank, and accounting. When those pieces match, the dashboard stops being decoration and becomes a management tool.

Questions it should answer

A good financial dashboard answers operational questions:

• How much did we sell today and how much was collected?
• Which part is pending settlement?
• Which e-CF receipts were accepted, rejected, or are pending?
• Which branch has margin deterioration?
• Which products rotate but leave little margin?
• How much cash do we need in the next 15 days?
• Which customers are delaying cash flow?

If the dashboard does not change decisions, it is extra.

The data layer

Before designing screens, we design a common model:

Sale

Includes product, quantity, price, discount, tax, branch, cashier, and channel.

Payment

Includes method, amount, reference, provider, state, expected settlement date, and reconciliation.

Receipt

Includes type, NCF/e-NCF, DGII status, issue date, fiscal amount, and relation to credit or debit notes.

Bank

Includes movement, account, amount, currency, raw description, probable counterparty, and association with payments.

Inventory

Includes cost, stock, transfers, waste, supplier, and replenishment.

With that model, reports come from a coherent source.

Metrics that actually help

Projected available cash

Current balance is not enough. The company needs expected inflows and outflows:

• Card settlements.
• Accounts receivable.
• Payroll.
• Suppliers.
• Taxes.
• Rent.
• Debt.

Projected cash flow avoids decisions based on a temporary balance.

Sales vs collection

A sale is not cash until it is collected and settled. Separating sale, payment, and deposit helps detect differences early.

e-CF fiscal health

For companies subject to electronic invoicing, the dashboard should show:

• Acceptance rate.
• Rejections by cause.
• Pending receipts.
• Average response time.
• Issued credit notes.

A fiscal problem detected late becomes an accounting problem.

Real product margin

Margin needs updated cost, discounts, taxes, payment fees, and returns. If it does not include those layers, the business may celebrate products that do not make money.

AI in the dashboard

AI should not replace metrics. It should help read them:

• “The Santiago branch margin dropped because discounts increased.”
• “There are 42 receipts pending DGII response.”
• “Projected cash falls below RD$X next Friday.”
• “This supplier raised average cost 8% in 30 days.”

The best financial AI does not write poems. It points to anomalies, explains likely causes, and suggests next steps.

How we do it at SSD

We start with integration, not visual design:

1. Connect sources.
2. Define the financial model.
3. Reconcile IDs across systems.
4. Validate data with accounting.
5. Create base metrics.
6. Build views by role.
7. Add alerts and explainable AI.

The owner needs summary. The accountant needs detail. Operations needs exceptions. One dashboard for everyone usually serves no one.

The result

When POS, e-CF, bank, and inventory talk, the company stops managing by stale intuition. It can see problems while they are still small.

That is the kind of financial infrastructure we are building for Dominican businesses: fewer manual reports, more decisions from reliable data.

Context sources

• DGII: electronic tax receipts e-CF
• Banco Central: payment systems