Skip to content
Free diagnosis
DSA Core · Contracts & Settlements

Contracts, certification and settlements.

Every work order and project turned into controlled money: price by contract and rate card, production validated with evidence, certification to the client, the invoice in your ERP and settlement to technicians and subcontractors without paying for what is not collected.

  • Back-to-backsubcontractors are paid what the client approves
  • Onceeach WO in one certification, one invoice and one settlement
  • ERPinvoices, self-billing and payroll variables, no retyping
Financial cockpit
DSA Core financial cockpit: quarterly production, not yet certified, receivables, settlements, actual margin and the funnel from executed to collected (demo data)
Work order close-out in the app with rate card items, zone factor, amount and required evidence (demo data)
Operating context

Where money is lost between execution and collection.

Contractors working to rate cards for operators, utilities and large clients do the work well. The margin escapes afterwards: in what is never certified, in what the client rejects and in what is paid before it is collected.

01Uncertified work

Closed work orders that never make it into the monthly certification.

Lost revenue
02Certifications in spreadsheets

Days of cross-checking work reports, rate card and client portal.

10-day closes
03Rejections without evidence

The client rejects and nobody can find the photo, reading or signature.

Adjustments accepted blind
04Out-of-date prices

Rate card versions, CPI and zone factors applied by hand.

Valuation errors
05Piece rate worked out by hand

Each technician’s production is recalculated in spreadsheets.

Claims and double payments
06Paying for what is not collected

Subcontractors are paid what they declare, even if the client rejects it.

Negative margin
07Typing invoices twice

Certified work is retyped in the sales and purchasing ERP.

Slower collection
08Unknown margin

You know contract revenue, not what each work order or zone earns.

Loss-making contracts

The ERP knows what was invoiced and paid. It does not know what completed work is still unbilled or what was paid without being collected.

Financial cycle

From contract to collection and payment, with a single reference record.

The reference record is the valued work order: contract, rate card items, zone factor, evidence, who did it and the certification, invoice and settlement it belongs to. Nothing is recalculated in a spreadsheet or typed twice.

  1. 1ContractRate card or unit prices, zones, versions and penalties
  2. 2ExecuteWOs and projects closed in the app with items and evidence
  3. 3ValidateAutomatic valuation, evidence and duplicate blocking
  4. 4CertifyBy chapter, with statement, partial approval and disputes
  5. 5Invoice and collectFrom approved work, in your ERP, with due dates and retentions
  6. 6SettleTechnicians to payroll and subcontractors to purchasing, back-to-back

The financial cockpit, every morning.

Where every euro produced sits: not yet certified, in dispute, approved but not invoiced, receivable and settled.

Financial cockpit
Financial cockpit with the funnel from executed to collected, where the money is stuck, actual margin by contract and upcoming milestones (demo data)
  1. 1Funnel: executed, validated, certified, approved, invoiced and collected.
  2. 2Where the money is stuck: uncertified, disputed, retentions and overdue.
  3. 3Actual margin by contract against target.
  4. 4Upcoming milestones: certification cut-offs, payroll, settlements and CPI.

One record for four teams. Operations executes, finance certifies and invoices, HR pays and purchasing settles. All four work on the same valued work order.

Contracts, rate cards and unit prices

The price of every job, beyond dispute.

Contracts with clients, with subcontractors and internal ones, each with its pricing model, term, budget, payment terms and retention.

Contract rate card
Framework contract rate card with items in points and price, client code, zone factors, SLA penalties and the version in force (demo data)
  1. 1Pricing model, point value, currency, tax, retention and payment terms.
  2. 2Dated version in force: certified work is never recalculated.
  3. 3Zone factor applied to each WO by location.
  4. 4SLA penalties: percentage, amount or no charge.
01Every pricing model

Points-based rate card, unit price list, per item or per route and stop, in one system. Each item carries the client’s code.

02Zone, SLA and CPI

Zone factors, penalties and price reviews applied automatically to each WO. CPI reviews are simulated before they are applied.

03Dated versions

Each WO is valued with the version in force on the day it was done. Changing version does not alter anything already certified.

Valued production

Only what can be proven gets certified.

Every work order and project measurement is valued with the rate card in force and the zone, and checked against the evidence required for the job type before it enters the certification.

Production validation
Production validation with WOs valued by points and zone, evidence and statuses validated, missing evidence, repeat, duplicate and outside rate card (demo data)
  1. 1Executed, validated, missing evidence, blocked and outside the rate card this month.
  2. 2The agent spots work already included in another WO and blocks it.
  3. 3Status of each WO: validated, missing evidence, repeat, duplicate or outside the rate card.
  4. 4Evidence required per job type: photo with serial, reading, location and signature.
01Projects by measurement

Project production goes through the same validation as work orders and into the same certification.

02Import

If WOs come from the client portal or another tool, they are imported and validated the same way.

03Technician alert

When evidence is missing, the technician is alerted on their phone and completes it from the WO.

Mobile app

Valuation starts when the work order is closed.

The technician picks the rate card items, attaches the evidence that job type requires and signs the statement with the client. Afterwards they check what they have produced on their phone.

  • Close-out statement. Items, quantities, zone factor and calculated amount. The WO cannot be closed if mandatory evidence is missing.
  • My production. What is validated, what still needs evidence, repeats and last month’s pay. Technicians know what is missing to get paid.
WO close-out in the app with rate card items, total points times zone factor and evidence with the client signature pending (demo data)
WO close-out and statement
My production in the app: estimated monthly variable pay, validated WOs, missing evidence, repeats and a prompt to attach a photo (demo data)
My production

Automatic checks before certifying and paying.

They hold the affected line and alert the person in charge. Everything else carries on.

01Duplicate WO

The same job declared in two WOs.

02Repeat within 30 days

Same address or equipment within 30 days.

03Outside the rate card

Item with no price in the contract.

04Incomplete evidence

Photo, reading or signature missing.

05Zero amount

A zero line with no justified reason.

06Inconsistent zone

Factor does not match the location.

07WO already certified

Already in another certification.

08Not approved by the client

Held back from the settlement.

09Double payment

WO already settled to the same payee.

10Expired documents

Subcontractor insurance or employment documents.

11Piece-rate cap

Variable pay above the monthly cap.

Protected rate card version

A price change never alters anything already certified.

Certification to the client

The monthly certification, in hours, not days.

It is generated from validated production, grouped by contract chapters and tracked until the client approves it and it is invoiced and collected.

Certification
Monthly certification with its status, chapters with quantity, points, amount and approval, financial summary with penalties and retention, and next step (demo data)
  1. 1Status: draft, sent, client review, approved, invoiced and collected.
  2. 2Approval by chapter: approved, under review or rejected.
  3. 3Gross, SLA penalties, retention and net to invoice.
  4. 4Next step: invoice what is approved, attach evidence and settle.
By contract chapter

Quantity, points and amount, with each WO’s detail one click away.

Statement in the client’s format

PDF statement and a spreadsheet in each client’s template, or upload to their portal.

Partial approval

You invoice what is approved without waiting for the rest.

Retentions and penalties

Retention with a release date and SLA penalties calculated.

Invoice sooner, collect sooner. Every day a certification takes to close is another day you are financing your client. The cockpit shows the days from execution to invoice per contract.

Disputes, invoicing and collection

Every rejection defended. Every invoice, no retyping.

Every line the client rejects is recorded with its reason, evidence and outcome. Recovered amounts go into the next certification.

Disputes and adjustments
Client disputes with reason, amount, age and status, rejection reasons for the year and the detail of a dispute with its evidence (demo data)
  1. 1The client’s classified reason for each rejected line.
  2. 2Age and status: resent, in negotiation, escalated, recovered or adjusted.
  3. 3Rejection reasons for the year, to fix the root cause.
  4. 4Evidence located and the agent’s proposed reply.
Invoicing and collection
Sales invoices generated from approved certifications with their ERP number, due date and status, receivables ageing and ERP connection (demo data)
Invoicing connected to the ERP

The invoice comes from the approved certification.

  • Client, taxes and lines go to the ERP; the tax number comes back.
  • Partial invoice from what is approved, without waiting for the rest.
  • Issuing company, currency and tax come from the contract.
  • Payments returned by the ERP and ageing by client.
  • Retentions to release and chasing overdue invoices.
Own technician settlement

Each technician is paid for what they produce, once.

Each technician’s validated production is valued with the internal rate card, quality deductions are applied and variable pay is sent to your payroll system.

Own technicians
Own technician settlement with WOs, points, hours, variable pay, deductions and amount payable, internal rate card rules and payroll export (demo data)
  1. 1Automatic deductions for repeats within 30 days or SLA breaches.
  2. 2Double payments: each WO is settled only once.
  3. 3Internal rate card: point value, guaranteed minimum and monthly cap.
  4. 4Payroll variables by employee, item and cost centre; period locked after export.
01Internal rate card

By points or by item, separate from the client’s rate card, with its own point value.

02No double payments

Each WO is settled once and the period locks after export. Later changes go through an adjustment.

03No disputes over pay

Technicians see their production on their phone and know which evidence is missing to get paid.

Subcontractor settlement

You pay what the client has approved.

Each subcontractor’s settlement comes from the same certification: its approved production, at its contract price, with retentions, penalties and valid documents. The self-billing proposal goes to the purchasing ERP.

Subcontractors
Subcontractor settlement with the back-to-back rule, executed versus approved, held amounts, deductions and amount payable, a subcontractor’s detail and checks before paying (demo data)
  1. 1Back-to-back rule: executed, approved by the client and held until approval.
  2. 2Per subcontractor: executed, approved, gross at its percentage, deductions and payable.
  3. 3Contract, penalties, subcontractor acknowledgement and documents.
  4. 4Checks before paying: double payments, documents and duplicate WOs.
01Back-to-back rule

Unapproved work is held and released when the client approves it. A subcontractor is never paid more than its percentage of approved work.

02Each subcontractor’s price

Percentage of the client’s rate card or its own price list, with retention and penalties.

03Acknowledgement and purchasing ERP

The subcontractor accepts the settlement in its portal and the self-billing invoice is validated in the purchasing ERP.

Valid documents before paying. If a subcontractor’s insurance or employment documents expire, its settlement is blocked until they are up to date.

Actual margin

What each contract, zone and work order earns.

Certified revenue minus settled labour, subcontractors, warehouse material and transport, with the actual cost charged to each work order and project.

Actual margin
Actual margin with certified revenue, labour, subcontractors, material and transport, margin by zone, WOs and projects with negative margin and agent proposals (demo data)
  1. 1Actual margin against the contract target.
  2. 2Margin by zone: whether the zone factor covers the real cost of working there.
  3. 3WOs and projects with negative margin and their cause.
  4. 4Agent proposals to renegotiate factor, price or training.
01Actual cost, not estimated

Settlements, warehouse material and transport are charged automatically to each WO.

02Cost build-up

Client price of each bundle against its standard cost and actuals.

03For negotiating

Data to renew or renegotiate contracts and prices with each client.

Automation

Six agents watching every euro, with human approval.

They work inside DSA Core, with each user’s permissions. They propose; no certification, invoice or payment runs without approval.

Rule-based agents
AI agent panel with each agent’s task and result, proposals awaiting approval and activity log for audit (demo data)
  1. 1Each agent with its task and what it has achieved.
  2. 2Pending proposals: nothing is applied until someone clicks Approve.
  3. 3Activity log: time, agent, task and who decided.

Available agents

01Leakage

Finds executed work that is not in any certification and proposes adding it.

02Evidence

Checks photos, readings, signature and location of each WO before certifying.

03Disputes

Classifies client rejections, finds the evidence and drafts the reply.

04Settlements

Detects double payments, duplicate WOs and settlements of unapproved work.

05Pricing

Watches CPI reviews, rate card versions and low-margin zones.

06Collections

Prioritises overdue receivables and prepares the claim with its certification.

Ask the assistantWhich August WOs are not certified?How much does Urban Gas owe me and since when?Which zone loses money for Operadora Nova?Which subcontractor has the most rejections?What changes if I apply the 3.1 % CPI?

AI governance

Inside DSA Core

Prices, margins and settlements are processed inside the DSA Core ecosystem, with logged access.

Role-based permissions

Technicians see their production; subcontractors, their settlement. Each agent only accesses what is authorised.

Human decision

No certification, invoice or payment runs without approval.

Traceability

Every query and proposal is logged; content labelled under Art. 50 of the AI Act.

Beyond certifying and settling

What it brings to operations, finance and management.

Work order import

From the client portal, your current tool or a spreadsheet.

The right issuer

The contract’s company invoices, with its own tax series.

Multi-currency and multi-tax

Currency and tax come from each contract.

Retentions

With a release date and a reminder to invoice them.

Subcontractor portal

Views its settlement and accepts it with an acknowledgement.

Bundles and cost build-up

Client price against own, subcontract and material cost.

Full audit trail

Every price change, approval and payment, with date and user.

Part of DSA Core 360

Work orders, projects, warehouse, fleet and transport.

Connects with Bids, tenders and contracts, Dashboard and intelligence and Company, HR and subcontractors.

Comparison

Against the usual approach.

Generic ERP and spreadsheetsDSA Core Contracts & Settlements
Contract pricesA spreadsheet per clientVersioned rate cards with zone factors
ProductionPaper reports or messagesValued WO with evidence
CertificationMonthly spreadsheetBy chapter, from validated WOs
Client rejectionsNot trackedDisputes with evidence and outcome
InvoicingRetypedFrom the certification, synced with the ERP
Technician piece rateManual calculationInternal rate card and payroll variables
SubcontractorsPaid what they declarePaid what the client approves
MarginAt year-endBy WO, zone and contract, every day
Artificial intelligenceNot availableBuilt-in agents, with human approval
Packages

Three ways to get it.

CertificationContracts and certification

Contracts, rate cards, production validation, certification and disputes.

RecommendedFull cycle

All of the above plus ERP invoicing, technician and subcontractor settlement, margin and rule-based agents.

The complete package
Full operationWith DSA Core 360

With work orders, projects, warehouse, fleet and transport on one platform.

SectorsTelecomsEnergy and utilitiesGas and waterInstallation and maintenanceConstructionTransport
ScopeEspañol · English · PortuguêsMulti-currency and multi-taxMulti-company and multi-country
Frequently asked questions

What people usually ask us before the demo.

Do I have to replace my ERP or payroll system?

No. DSA Core sends sales invoices and purchase self-billing invoices to the ERP and receives the tax number and payments back. It sends each technician’s variable pay to the payroll system by employee, item and cost centre.

Does it work if my work orders live in another system?

Yes. Work orders are imported from the client portal, your current tool or a spreadsheet. You can start with certification and settlements and extend to the rest of DSA Core later.

What happens to certified work if I change the rate card or apply CPI?

Nothing. Each work order is valued with the rate card version in force on the day it was done, and a new version does not change anything already certified. CPI price reviews are simulated before they are applied.

How do I avoid paying a subcontractor for work the client has not approved?

With the back-to-back rule: technicians and subcontractors are only paid for what the client has approved. Work done but not approved is held and released when the client approves it.

How do I avoid invoicing or paying for the same work order twice?

Each work order goes into one certification, one invoice and one settlement per payee, once. The system checks this before every document and keeps the record for audit.

Can I invoice a certification that is only partly approved?

Yes. Approval is recorded by chapter and by line, and you invoice what is approved without waiting for the rest. Rejected lines go to disputes with their reason and evidence.

Does it handle points-based rate cards and unit prices?

Yes. Points-based rate cards with a point value, unit price lists, price per item or per route and stop, or a mixed model. With zone factors and SLA penalties applied to each work order.

Do the rule-based agents act on their own?

No. The agents propose and no certification, invoice or payment is executed without human approval. Each agent only accesses information the user is authorised to see, and every query and proposal is logged.

30-minute demo

We will show you in 30 minutes, with a case like yours.

  1. Demo with a month of sample work orders from your sector
  2. Loading your rate card and zones
  3. Pilot with one contract and one subcontractor
  4. Roll-out connected to your ERP and payroll

DSA Core connects to your ERP and payroll system; it does not replace them.

David Soler, founder of DSA Nexus
The first meeting is with David Soler, founder.WhatsApp +34 615 160 114 · hola@dsanexus.com
Demo or brochure

Request your 30-minute demo

A person will reply within 24 working hours.

Free diagnosisWhatsApp