Professional payment operations
Know the payment record before you accept the work.
An IT Modality engagement defines how work is measured, approved, invoiced, corrected, paid, and evidenced. The values vary by scope; the required fields and change discipline do not.
ForExperienced independent professionals
FocusAssessment, readiness, engagement operations, and support
The written package names every material field.
Table — scroll horizontally to review every column.
| Field | What the professional receives |
|---|---|
| Rate and unit | The agreed amount and whether it applies to an hour, day, milestone, fixed deliverable, retainer, or another defined unit |
| Currency | The contract and payment currency and any permitted alternative |
| Eligible work | The scope, service window, milestone, deliverable, expense, or other condition that may be submitted |
| Evidence | The time record, deliverable, acceptance evidence, invoice, receipt, or other support required |
| Approval | The assigned approver, review sequence, rejection reason, and correction path |
| Submission | The invoice or record format, destination, cadence, cutoff, and reference requirements |
| Payment event | The date, event, or rule that makes an approved amount payable under the agreement |
| FX | The conversion source or provider, conversion point, and which party bears the defined cost or variance |
| Transfer fees | Which sending, intermediary, receiving, or provider fees each party bears |
| Expenses | The categories, preapproval, evidence, currency, limits, and reimbursement rule that apply |
| Corrections | How an incorrect, incomplete, disputed, or rejected record is returned, corrected, approved, and retained |
| Remittance record | The statement, reference, invoice state, and applicable tax or reporting document the professional receives |
| Escalation | The owner and protected route for an overdue, rejected, mismatched, missing, or otherwise disputed record |
Payment moves through attributable records.
Work or milestone evidence is created under the accepted scope.
The assigned owner reviews it against the written approval and acceptance conditions.
A valid invoice or submission is recorded with the applicable currency, unit, and reference.
Exceptions are returned with a reason and preserve both the original and corrected record.
The payment event is applied exactly as stated in the agreement.
Remittance is recorded with the reference and documents the professional is entitled to receive.
A portal view can summarize the protected record, but it does not silently change the agreement, invent approval, or erase an exception history.
Commercial changes require the same discipline as scope changes.
A different rate, unit, currency, eligible-work rule, approval owner, submission sequence, payment event, FX treatment, transfer-fee allocation, or expense condition becomes effective only through the applicable written change process.
An informal client request does not authorize uncompensated or out-of-scope work. The professional should record the request and route it to the named scope and commercial owner before proceeding.
No professional pays for access to work.
Professionals pay no fee to apply, complete The Rigors, enter the network, be placed on a client shortlist, or accept an engagement. Payment to the Academy is separate and never changes professional assessment or selection.
An engagement-specific rate is agreed before commitment. IT Modality does not reduce that agreed professional rate because a client later negotiates IT Modality's commercial rate down.
Individual legal, tax, banking, and FX outcomes remain individual.
IT Modality supplies the contracting, invoice, approval, remittance, and reporting records it is required or agrees to provide. Professionals remain responsible for obtaining their own advice about registration, tax, banking, foreign exchange, and local obligations.
This guide does not promise a tax rate, withholding result, remittance treatment, bank outcome, provider availability, payment amount, minimum hours, duration, or income.
Inspect the surrounding controls.
Review the grievance process
Review how engagements run
Record boundary: Engagement-specific rates, invoices, approvals, payment status, bank details, provider details, tax records, and remittance references remain in the written package and protected operating system. None belongs on this public page.