Projects — Complete User Guide — Two Accounts Web
Comprehensive guide for managing projects, tracking project income and expenses, and analyzing project profitability
Table of Contents
- What Are Projects?
- Enabling the Tab via Customize Menu
- Field-by-Field Guide
- Creating a Project
- Using Projects on Transactions
- Project Reports
- Accounting Impact
- Opening Balances
- Sample Data and Report Output
- Accounting Regulation Compliance
1. What Are Projects?
A Project is a classification dimension that groups transactions across multiple documents. Projects allow you to track the financial performance of specific initiatives, contracts, or work streams independently from the rest of the business.
Projects are different from transaction types — they don't create GL entries or change accounting. Instead, they add a reporting dimension that lets you filter and group transactions by project.
Projects are used for:
- Contract profitability — tracking income and expenses for a specific customer contract
- Internal initiatives — monitoring the cost of an internal project (e.g., office renovation, IT implementation)
- Grant tracking — separating grant-funded activities from regular operations
- Capital projects — tracking costs for asset construction before capitalization
- Event management — budgeting and tracking a specific event or campaign
2. Enabling the Tab via Customize Menu
Projects is a standalone tab that does NOT depend on other tabs. To enable:
- Open Customize Menu
- Find "Projects" in the list of available tabs
- Toggle to Visible
- Click Save
Once enabled:
- Projects appears in the navigation bar — the main listing of all projects with income, expenses, and profitability columns
- The Project field becomes available on transaction lines throughout the system
3. Field-by-Field Guide
| Field | Type | Required | Description |
|---|---|---|---|
| Name | Text | Yes | The project name. This is the primary identifier shown in dropdowns, reports, and transaction lines throughout the system. |
| Inactive | Checkbox | No | Mark the project as inactive to hide it from dropdowns on new transactions. Existing transactions linked to this project are unaffected — historical data is preserved. |
| Custom Fields | Configurable | No | Additional fields added via Settings > Custom Fields with Placement = Projects. Useful for capturing project-specific data such as client name, budget amount, start date, or contract reference. |
4. Creating a Project
- Go to Projects > New Project
- Enter the Name (required)
- Add Custom Fields if configured
- Save
Projects can also be made inactive later by editing and checking the Inactive checkbox. Inactive projects are hidden from dropdowns on new transactions.
5. Using Projects on Transactions
5.1 Where the Project Field Appears
The Project field appears on the line items of the following transaction types, provided the selected GL account supports projects:
| Transaction Type | Section |
|---|---|
| Sales Invoice | Sales / Customer Invoicing |
| Purchase Invoice | Purchases / Supplier Invoicing |
| Receipt | Cash In / Customer Payments |
| Payment | Cash Out / Supplier Payments |
| Credit Note | Sales Returns / Customer Credits |
| Debit Note | Purchase Returns / Supplier Debits |
| Journal Entry | General Adjustments |
| Expense Claim | Employee Expense Reimbursement |
| Purchase Order | Ordering Goods/Services |
| Payslip (Earnings) | Payroll — Labour Allocation |
| Inventory Write-Off | Inventory Adjustments |
| Letter of Credit (Line) | Import LC Cost Allocation |
| Letter of Credit (Header) | Import LC Overview |
| Export Letter of Credit (Header) | Export LC Overview |
| Sales Quote, Sales Order | Pre-sales Documents |
| Purchase Quote | Pre-purchase Documents |
5.2 Income Classification
A transaction line assigned to a Project is classified as Income when:
- The line has a Customer reference (i.e., it originates from a Sales Invoice, Receipt from customer, or Credit Note)
- The line is not a project cost (see below)
Income lines appear in the Income column on the Projects listing and can be drilled down via the income transactions viewer.
5.3 Cost Classification
A transaction line assigned to a Project is classified as Cost when any of these conditions apply:
- The line is marked as Cost of Goods Sold
- The line is a Billable Expense
- The line has no Customer reference and is not a Receipt (i.e., it's a supplier invoice, payment, expense, or adjustment)
Cost lines appear in the Expenses column on the Projects listing and can be drilled down via the incurred cost transactions viewer.
5.4 Projects vs Divisions
Projects and Divisions are independent classification dimensions that can coexist on the same transaction line:
| Aspect | Project | Division |
|---|---|---|
| Purpose | Track specific initiatives or contracts | Organizational structure (departments, branches) |
| Scope | Temporary — exists for the project duration | Permanent — reflects the organizational hierarchy |
| Profit tracking | ✅ Income — Costs — Profit per project | Not directly (used for divisional reporting) |
| GL accounts affected | Most P&L and BS accounts (where projects are supported) | Division-enabled accounts |
| Availability | Single field on transaction lines | Single field on transaction lines |
Both can be set simultaneously on the same line — a transaction can belong to a Division AND a Project at the same time for complete reporting.
5.5 LC-Related Transactions and Projects
Letters of Credit — both Import and Export — fully support Project assignment. The Project field can be set at the LC header level or on individual cost lines, and the value flows through to the general ledger transactions created by the LC.
Import LC (Letter of Credit)
Project resolution follows this priority:
- Cost line
Projectfield — if set on the individual cost line, this takes highest priority - LC header
Projectfield — used as fallback for cost lines that do not have their own Project - AP/LCP balancing entries — always use the LC header Project
Import LC GL entries have Supplier reference but no Customer reference. Per the project cost classification rules, all Import LC entries with a Project assigned are classified as Costs on the Project listing.
Export LC (ExportLetterOfCredit)
The LC header Project field is used for all GL entries created by the Export LC, including fee entries. The Export LC GL entries carry a Customer reference (the exporter), so they are classified as Income per the project classification rules.
Export LC Receipt (ExportLCReceipt)
The ExportLCReceipt reads its Project from the linked Export Letter of Credit's header Project. All four GL entries it creates carry this Project and are classified as Income (they all have a Customer reference).
- Cr ExportLCReceivable → +Income (clears receivable from bank)
- Dr ExportLCARClearing → −Income (removes temporary credit)
- Dr CashAtBank → recorded as Income (cash received)
- Cr AccountsReceivable (linked SI) → +Income (clears SI balance)
Summary of LC classification in Projects:
| LC Document | Project Source | IsGLTx? | Appears in Projects? | Classification |
|---|---|---|---|---|
| Import LC cost lines | Cost line → header fallback | ✅ true | ✅ Yes | Cost (Supplier, no Customer) |
| Import LC AP/LCP balancing | Header Project | ✅ true | ✅ Yes | Cost (no Customer) |
| Export LC (all entries) | Header Project | ✅ true | ✅ Yes | Income (has Customer) |
| Export LC Receipt (4 entries) | Inherited from linked ELC | ✅ true | ✅ Yes | Income (has Customer) |
6. Project Reports
6.1 Project Listing
The main Projects page shows all projects with their financial performance:
| Column | Description | Calculation |
|---|---|---|
| Name | Project name | From the Project record |
| Income | Total income attributed to the project | Sum of all GL transaction amounts where the line has a Project reference and is NOT classified as a project cost. Clickable to drill into income transactions. |
| Expenses | Total costs attributed to the project | Sum of all GL transaction amounts where the line has a Project reference and IS classified as a project cost. Clickable to drill into cost transactions. |
| Profit | Net project profitability | Income minus Expenses. Clickable to open the Project P&L report. |
| Purchase Orders | Total value of open purchase orders for this project | Sum of Purchase Order amounts that are linked to this project, minus amounts already invoiced. Clickable to drill into purchase orders. |
| Revised Profit | Projected profit considering open PO commitments | Profit minus Purchase Orders (i.e., current profit adjusted for committed but not yet invoiced PO amounts). |
6.2 Project Profit and Loss Report
Clicking the Profit value on the Projects listing opens the Project P&L Report. This report shows:
- Income section — all transaction lines grouped by GL account, showing income generated by the project
- Expenses section — all cost lines grouped by GL account, showing costs incurred for the project
- Profit total — the net result (Income minus Expenses) for the project
6.3 Income Drill-Down
Clicking the Income value opens a transaction viewer showing every GL transaction classified as income for that project. The viewer shows: Date, Reference, Description, Debit/Credit amounts, and running balance. Uses sign reversal (MultipleByOne = true) for display.
6.4 Cost Drill-Down
Clicking the Expenses value opens a transaction viewer showing every GL transaction classified as a project cost. This includes the Cost of Goods Sold calculation to ensure all inventory-related costs are captured.
6.5 Purchase Orders Grid
Clicking the Purchase Orders value opens a grid showing all purchase orders linked to this project, with columns: Date, PO Reference, Supplier, Project, Order Amount, Invoiced Amount, and Uninvoiced Balance.
7. Accounting Impact
7.1 How Income and Costs Are Classified
The system automatically determines whether a project-tagged transaction line is income or cost based on these rules:
A line is classified as a PROJECT COST if:
- It is a Cost of Goods Sold transaction, OR
- It is a Billable Expense, OR
- It has no Customer reference AND is not a Receipt
A line is classified as PROJECT INCOME if:
- It has a Customer reference (from Sales Invoice, Receipt, Credit Note)
- AND it is NOT classified as a project cost
All other project-tagged lines are classified as income.
The system does NOT create separate GL entries for projects — projects are a reporting dimension only. The underlying GL posting follows the standard rules for each transaction type (Sales Invoice creates Dr AR / Cr Revenue; Purchase Invoice creates Dr Expense / Cr AP; etc.).
7.2 Profitability Calculation
Project Profit = Project Income − Project Expenses
Revised Profit = Project Profit − Open Purchase Orders
Where:
Project Income = Sum of all amounts for income-classified Project lines
Project Expenses = Sum of all amounts for cost-classified Project lines
Open Purchase Orders = PO amounts linked to the Project minus invoiced amounts
All amounts are calculated in the base currency. The Income and Expenses values are clickable for drill-down to the underlying transactions.
8. Opening Balances
Projects cannot have opening balances. The Project listing derives all its financial data from transaction lines that have a Project assigned. There is no "opening balance" field on a Project record — all project income and expenses are built up from individual transactions over time.
If you need to set a starting position for a project that existed before the system was implemented, create a Journal Entry with:
- A line debiting or crediting the appropriate P&L accounts with the project assigned
- A balancing line to Retained Earnings (or Suspense)
- The Project field set on the line(s)
This will correctly seed the project's income and cost balances from the opening date.
9. Sample Data and Report Output
Setup
| Item | Details |
|---|---|
| Base Currency | BDT |
| Project | Office Renovation Project |
| Customer | Internal (no customer — project is internal) |
| Supplier | ConstructCo Ltd (contractor) |
Transactions
| Date | Type | Line Account | Amount | Project Classification |
|---|---|---|---|---|
| 01-Jun-2026 | Purchase Invoice PI-001 | Renovation Expense (P&L) | 500,000.00 Dr | Cost (no customer, not a receipt) |
| 15-Jun-2026 | Payment PMT-001 | Cash at Bank | 500,000.00 Cr | Not a project line (bank account) |
| 20-Jun-2026 | Journal Entry JE-001 | Consulting Income (P&L) | 50,000.00 Cr | Income (no cost, no supplier — default income) |
| 25-Jun-2026 | Purchase Order PO-001 | Furniture Expense | 100,000.00 (order value) | Not yet invoiced — appears in Purchase Orders column |
GL Transactions Created
PI-001 (ConstructCo Ltd — Renovation):
Dr Renovation Expense 500,000.00
Cr Accounts Payable (ConstructCo) 500,000.00
Project assigned: Office Renovation
Classification: COST (no customer, not a receipt)
PMT-001 (Payment to ConstructCo):
Dr Accounts Payable (ConstructCo) 500,000.00
Cr Cash at Bank 500,000.00
No Project assigned (bank account — projects not supported for this account type)
JE-001 (Consulting Income):
Dr Accounts Receivable 50,000.00
Cr Consulting Income 50,000.00
Project assigned: Office Renovation
Classification: INCOME (not a cost)
Project Listing — Office Renovation
| Column | Amount | Detail |
|---|---|---|
| Income | 50,000.00 | JE-001 Consulting Income |
| Expenses | 500,000.00 | PI-001 Renovation Expense |
| Profit | −450,000.00 | Income 50,000 − Expenses 500,000 |
| Purchase Orders | 100,000.00 | PO-001 Furniture (not yet invoiced) |
| Revised Profit | −550,000.00 | Profit −450,000 − PO 100,000 |
Calculation Verification
Income:
JE-001 Consulting Income: 50,000.00
Total Income: 50,000.00 ✓
Expenses:
PI-001 Renovation Expense: 500,000.00
Total Expenses: 500,000.00 ✓
Profit: 50,000.00 − 500,000.00 = −450,000.00 ✓
Revised Profit: −450,000.00 − 100,000.00 = −550,000.00 ✓
DR = CR Verification
PI-001 (Project cost):
Dr Renovation Expense 500,000.00
Cr Accounts Payable 500,000.00
DR = CR: 500,000.00 − 500,000.00 = 0.00 ✓
PMT-001 (Payment — no project):
Dr Accounts Payable 500,000.00
Cr Cash at Bank 500,000.00
DR = CR: 500,000.00 − 500,000.00 = 0.00 ✓
JE-001 (Project income):
Dr Accounts Receivable 50,000.00
Cr Consulting Income 50,000.00
DR = CR: 50,000.00 − 50,000.00 = 0.00 ✓
Scenario B — Import LC — Header-Based Project
Setting Project once on the LC header cascades to all cost lines and balancing entries.
| Field | Value |
|---|---|
| LC-001 header Project | "Warehouse Expansion" ← set ONCE on the header |
| LC Margin | 30% |
| CIF cost line | Widget-X, Amount: $15,000 @ 110 = 16,50,000 BDT, Project: (inherited from header) |
| Duties cost line | CD + RD + SD + CVD, Amount: 10,06,500 BDT, Project: (inherited from header) |
| Landed cost line | Freight + Insurance, Amount: 2,12,750 BDT, Project: (inherited from header) |
GL Transactions with Project Assignment
LC-001 CIF cost line (Widget-X, inventory):
Dr Inventory On Hand 16,50,000
Cr AP / LCP (via balancing) 16,50,000
Project: "Warehouse Expansion" (inherited from LC header)
Classification: COST (Supplier reference, no Customer)
LC-001 Duties cost line (Period Cost):
Dr LC Expense (Duties) 10,06,500
Cr AP / LCP (via balancing) 10,06,500
Project: "Warehouse Expansion" (inherited from LC header)
Classification: COST
LC-001 Landed cost line (Landed Cost):
Dr Inventory On Hand (Landed) 2,12,750
Cr AP / LCP (via balancing) 2,12,750
Project: "Warehouse Expansion" (inherited from LC header)
Classification: COST
--- Liability split at 30% margin ---
LC-001 AP Balancing entry (margin + other costs):
Dr Accounts Payable 17,14,250
Cr Cash / LC Payable 17,14,250
Project: "Warehouse Expansion" (LC header Project — balancing always uses header)
Classification: COST (no Customer)
Composition: CIF margin 4,95,000 + Duties 10,06,500 + Landed 2,12,750
LC-001 LCP Balancing entry (financed portion):
Dr Letter of Credit Payable 11,55,000
Cr Cash 11,55,000
Project: "Warehouse Expansion" (LC header Project)
Classification: COST (no Customer)
Composition: CIF financed portion 70% = 11,55,000
Verification: AP 17,14,250 + LCP 11,55,000 = 28,69,250 = Total cost lines ✓
Scenario B2 — Import LC — Line-Level Project Override
When LC costs need to be split across multiple Projects, set individual Projects on specific cost lines.
| Field | Value |
|---|---|
| LC-002 header Project | "Warehouse Expansion" ← default project |
| CIF cost line | Widget-X, Amount: $15,000 @ 110, Project = "Warehouse Expansion" ← explicit on line |
| Duties cost line | Amount: 10,06,500 BDT, Project = "Warehouse Expansion" ← explicit on line |
| Landed cost line | Freight + Insurance, Amount: 2,12,750 BDT, Project = "Customs Clearance Project" ← DIFFERENT project! |
GL Transactions — Line-Level Override
LC-002 CIF cost line:
Project: "Warehouse Expansion" (from cost line — same as header) ✅
LC-002 Duties cost line:
Project: "Warehouse Expansion" (from cost line) ✅
LC-002 Landed cost line:
Project: "Customs Clearance Project" (from cost line — overrides header!) ✅
LC-002 AP Balancing entry (17,14,250):
Project: "Warehouse Expansion" (uses header Project, not cost line) ✅
Note: The 17,14,250 total includes the landed cost of 2,12,750 that belongs to
"Customs Clearance Project" — but the balancing entry posts all to the header Project.
LC-002 LCP Balancing entry (11,55,000):
Project: "Warehouse Expansion" (uses header Project) ✅
Project Listing — Warehouse Expansion (Scenario B)
| Column | Amount | Detail |
|---|---|---|
| Income | 0.00 | No income entries — all LC entries classified as Cost |
| Expenses | 28,69,250.00 | CIF 16,50,000 + Duties 10,06,500 + Landed 2,12,750 |
| Profit | −28,69,250.00 | Income 0 − Expenses 28,69,250 |
| Purchase Orders | 0.00 | No POs linked |
| Revised Profit | −28,69,250.00 | Same as Profit |
Debit entries (costs): +16,50,000 + 10,06,500 + 2,12,750 = +28,69,250
Credit entries (liability): −17,14,250 − 11,55,000 = −28,69,250
Net incurred costs: 0.00
To see the actual resource costs of the LC, use the Expenses drill-down (click the Expenses value) and review the debit-side entries (Inventory, LC Expense accounts). The credit-side entries (AP, LCP) represent how the costs were financed and do not reflect additional project resource consumption.Calculation verification:
Cost lines (debit entries):
CIF cost line: 16,50,000
Duties cost line: 10,06,500
Landed cost line: 2,12,750
Total costs incurred: 28,69,250
Balancing entries (credit entries):
AP balancing: −17,14,250
LCP balancing: −11,55,000
Total balancing: −28,69,250
Net in Project listing (costs + balancing): 0.00
(Dr + Cr entries cancel — both carry the Project)
Use the Expenses drill-down to see actual costs.
Profit: 0.00 − 0.00 = 0.00 (before drill-down filter)
Actual resource costs: 28,69,250 (visible in drill-down)
Scenario C — Export LC with Project "Export Sales Q2"
| Field | Value |
|---|---|
| ELC-001 | $10,000 Export LC, Project = "Export Sales Q2", Customer: Overseas Buyer Ltd |
| Fees | Bank commission $200 + Swift $50 = $250 total fees |
| Exchange Rate | 110 BDT/USD |
| Sales Invoice SI-002 | $10,000 @ 110 = 11,00,000 BDT, Project = "Export Sales Q2" |
GL Transactions with Project Assignment
ELC-001 — Dr ExportLCReceivable ($10,000 @ 110):
Dr Export LC Receivable 11,00,000
Cr Export LC AR Clearing 11,00,000
Project: "Export Sales Q2" (ELC header)
Classification: INCOME (has Customer reference)
ELC-001 — Fee entries ($250 @ 110):
Dr LC Expense (Bank Fees) 27,500
Cr Export LC Receivable 27,500
Project: "Export Sales Q2" (ELC header)
Classification: INCOME (has Customer reference)
SI-002 — Revenue recognition ($10,000 @ 110):
Dr Accounts Receivable 11,00,000
Cr Export Revenue 11,00,000
Project: "Export Sales Q2"
Classification: INCOME (has Customer reference)
ExportLCReceipt ELCR-001 ($9,750 net receipt @ 110):
Dr Cash at Bank 10,72,500
Dr Export LC AR Clearing 10,72,500
Cr Export LC Receivable 10,72,500
Cr Accounts Receivable (SI-002) 10,72,500
Project: "Export Sales Q2" (inherited from linked ELC)
Classification: INCOME (all 4 entries have Customer reference)
Project Listing — Export Sales Q2
| Column | Amount | Detail |
|---|---|---|
| Income | 11,00,000.00 | SI-002 Export Revenue (ELC entries net to zero within the LC itself) |
| Expenses | 0.00 | No cost entries — ELC and ExportLCReceipt all classified as Income |
| Profit | 11,00,000.00 | Income 11,00,000 − Expenses 0 |
| Purchase Orders | 0.00 | No POs linked |
| Revised Profit | 11,00,000.00 | Same as Profit |
Dr ExportLCReceivable +11,00,000 → +Income (sign-flipped)
Cr ExportLCARClearing −11,00,000 → −Income (sign-flipped)
Cr ExportLCReceivable(fee) −27,500 → +Income
Dr LCExpense +27,500 → −Income
Cr ExportLCReceivable −10,72,500 → +Income (receipt)
Dr ExportLCARClearing +10,72,500 → −Income (receipt)
Cr AccountsReceivable −10,72,500 → +Income (receipt)
Dr CashAtBank +10,72,500 → −Income (receipt)
Net Income from all ELC entries: 0.00
The true project revenue of 11,00,000.00 comes from Sales Invoice SI-002. This is the correct behavior — the Export LC is a financing mechanism, not a revenue-generating transaction. The revenue is recognized when the Sales Invoice is created.Calculation verification:
Scenario B — Warehouse Expansion:
Income: 0.00
Expenses: 64,54,975.00 (all LC costs + balancing entries)
Profit: −64,54,975.00 ✓
Scenario C — Export Sales Q2:
Income: 11,00,000.00 (SI-002 revenue — ELC entries net to zero)
Expenses: 0.00
Profit: 11,00,000.00 ✓
DR = CR Verification — LC Scenarios
LC-001 CIF cost line:
Dr Inventory On Hand 16,50,000
Cr AP / LCP balancing 16,50,000
DR = CR: 16,50,000 − 16,50,000 = 0.00 ✓
LC-001 Ship balancing:
Dr AP balancing 24,30,725
Dr LCP balancing 11,55,000
Cr Cash 35,85,725
DR = CR: 24,30,725 + 11,55,000 − 35,85,725 = 0.00 ✓
ELC-001 Issuance:
Dr Export LC Receivable 11,00,000
Cr Export LC AR Clearing 11,00,000
DR = CR: 11,00,000 − 11,00,000 = 0.00 ✓
ELC-001 Fee entry:
Dr LC Expense (Bank Fees) 27,500
Cr Export LC Receivable 27,500
DR = CR: 27,500 − 27,500 = 0.00 ✓
SI-002 Revenue:
Dr Accounts Receivable 11,00,000
Cr Export Revenue 11,00,000
DR = CR: 11,00,000 − 11,00,000 = 0.00 ✓
ExportLCReceipt ELCR-001:
Dr Cash at Bank 10,72,500
Dr Export LC AR Clearing 10,72,500
Cr Export LC Receivable 10,72,500
Cr Accounts Receivable 10,72,500
DR = CR: 10,72,500 + 10,72,500 − 10,72,500 − 10,72,500 = 0.00 ✓
10.1 IAS 11 / IFRS 15 — Construction Contracts / Revenue
Requirement (IFRS 15 §9): Revenue is recognized when control of goods or services transfers to the customer. For long-term contracts, revenue may be recognized over time if certain criteria are met.
How this system complies: Projects provide the tracking dimension for contract revenue and costs. The Project P&L report shows the complete financial picture of each contract, supporting both point-in-time and over-time revenue recognition models. The Purchase Orders column shows committed costs not yet recognized, providing visibility into future obligations.
10.2 IAS 2 — Inventories (Project Costs)
Requirement (§12-14): The cost of inventories includes costs directly attributable to the production process. Abnormal costs are expensed as incurred.
How this system complies: The project cost classification correctly captures all direct costs assigned to a project through transaction lines. Cost of Goods Sold transactions are automatically classified as project costs. The Cost of Goods Sold calculation includes project-tagged inventory movements, ensuring inventory-related project costs are fully captured.
10.3 IAS 37 — Provisions, Contingent Liabilities and Contingent Assets
Requirement (§14): A provision is recognized when a present obligation exists from a past event, payment is probable, and the amount can be reliably estimated.
How this system complies: The Purchase Orders column on the Projects listing shows committed but not yet invoiced amounts. This provides visibility into future obligations related to each project, supporting the assessment of whether a provision for onerous contracts (IAS 37 §66) may be required.
10.4 IAS 1 — Presentation of Financial Statements
Requirement (§10-11): An entity may present additional information beyond the minimum requirements. Segment reporting provides useful information about different business activities.
How this system complies: Projects add a reporting dimension that segments income and expenses by project. The Project P&L report provides disaggregated financial information, supporting internal management reporting and decision-making. Projects complement, rather than replace, the standard financial statements.
10.5 DR = CR Verification
Every transaction with a Project assignment follows standard double-entry rules.
The Project field is a reporting dimension only — it does NOT affect the
underlying GL posting or double-entry balance.
PI-001: Dr Renovation Expense 500,000 / Cr AP 500,000
Project assigned: Office Renovation
DR = CR: 500,000 − 500,000 = 0.00 ✓
PMT-001: Dr AP 500,000 / Cr Cash 500,000
No Project (bank account)
DR = CR: 500,000 − 500,000 = 0.00 ✓
JE-001: Dr AR 50,000 / Cr Consulting Income 50,000
Project assigned: Office Renovation
DR = CR: 50,000 − 50,000 = 0.00 ✓
10.6 Relevant but Not Applicable
- IFRS 16 (Leases): Lease costs can be assigned to a Project via the Project field on transaction lines, but the Project itself is not a lease arrangement.
- IAS 7 (Cash Flow Statement): The Project dimension does not affect cash flow classification. Project-related cash flows appear in the same CFS categories as non-project transactions.
- IAS 21 (Foreign Exchange): Projects do not have a currency — they inherit the transaction's currency from the customer, supplier, or bank account used.
End of Projects Guide