Purpose
Effective Date on a Deal Transaction is the date a transaction is considered true for business, regulatory, and reporting purposes — regardless of when Built recorded it. Effective Date is now stored and displayed as a calendar date with no time component, so the date entered is the date shown everywhere in the application and in reporting.
A separate system-generated field, Posted Time, captures when Built recorded the transaction. This keeps the business date and the system chronology as two distinct facts.
Key Features
Effective Date is a calendar date: Effective Date is stored and displayed as a date only. It does not shift with the viewer's timezone.
Backdating & future dating: Effective Date can be set to any date in the past. Effective Date can be scheduled up to 10 days in the future, in order to account for holidays and cutoff times.
Posted time records system chronology: Posted time is system-generated and captures when the transaction was recorded in Built.
How It Works
Two fields work together on every Deal Transaction:
Field | Set by | What it represents |
|---|---|---|
Effective Date | User provided | The calendar date the transaction is effective for business and reporting purposes. Can be 10 days into the future, today, or in the past. Date only — no time, no timezone conversion. |
Posted time | System generated | When Built recorded the transaction. Used to sort transactions that share the same Effective Date. |
Entering a transaction in Built
Open a deal and go to Transactions.
Select New Transaction.
Enter the Effective Date. This can be a future date (10 days), the current date, or a date in the past.
Complete the remaining transaction details and save. Built records Posted time automatically.
The Transactions list displays an Effective Date column showing the date only. Transactions with the same Effective Date are ordered by Posted time.
Receiving transactions by integration
Integrations from third-party servicing systems require an Effective Date with no time. Built now stores the supplied date exactly as provided.
Benefits
Effective Dates match business intent.
Transaction dates in Built reconcile against third-party systems.
Backdating a transaction no longer requires supplying or inventing a time.
Intra-day sequence is still available through Posted time, so same-day draws and payments remain distinguishable.
Reporting and application views draw on the same date value, so they agree with each other.
Best Practices
Set Effective Date to the date the transaction is effective for the business — the accrual or posting date the deal parties recognize — not the date it was entered into Built.
When supplying transactions through an integration, send the Effective Date as a plain calendar date. There is no need to add a time or timezone offset.