Payment Posting

Validate direct payment posting

Validates direct post-payment input against one organization-scoped remittance claim and returns a safe simulated acceptance response without creating Payment records or mutating claim balances.

POSTNeeds publication reviewPayment or creditPayment PostingoperationId: postPaymentPostingPaymenthttps://dev-api.quickintell.com/api/v1/payment-posting/remittance-claims/{remittanceClaimId}/post-payment

Needs publication reviewPayment or creditClaims and remittances

Route status

Needs publication review

The endpoint contract is visible, but QuickRCM has not approved it yet for normal production API use.

Publication status

Needs publication review

Requires product, security/compliance, tenancy, side-effect, or module-owner approval before production public API use. Also requires E2 side-effect policy and E3 async and idempotency policy before production recipes, SDK inclusion, or try-out access.

Authentication

Bearer API key declared

OpenAPI declares bearer API-key security for this operation.

Tenant context

API-key organization

API-key organization context is authoritative; request organizationId is not a public tenant selector.

Side-effect summary

Payment or credit

May affect payments, credits, refunds, voids, or financial posting. Requires explicit product approval before publication.

Source artifact

docs/openapi/openapi.json

OpenAPI 3.1.0; API 1.0.0.

When to use this endpoint

Use this page as an internal baseline for the claims and remittances contract generated for POST /api/v1/payment-posting/remittance-claims/{remittanceClaimId}/post-payment. External use still depends on route classification, release evidence, and endpoint-specific side-effect approval.

What this does now

Shows the generated OpenAPI shape for POST /api/v1/payment-posting/remittance-claims/{remittanceClaimId}/post-payment, but keeps the route out of ordinary production API positioning until review is complete.

What this does not do

Does not prove external GA readiness, SDK readiness, live production execution, or complete module behavior. Mutating behavior still needs side-effect and retry evidence.

Not public from this page

Do not publish this endpoint as an ordinary developer API until its unresolved decisions are closed.

Headers and tenancy

Current headers and tenant authority. Target headers stay labeled as future until OpenAPI and release evidence declare them.

Header	Required	Current status	Notes
Authorization	Yes	Current	Bearer <QUICKRCM_API_KEY>. OpenAPI security: bearerAuth.
Idempotency-Key	No	Target/future	Do not claim universal header support until E3 and OpenAPI metadata exist.
X-Request-Id	No	Target/future	Use for support correlation only after approved; not declared as a standard OpenAPI header today.

Required scopes

Unclassified until E6 route metadata exists; do not infer scopes from route names.

Wrong-org behavior

Tenant-safe 404, empty list, or 403 is endpoint-specific and remains an evidence gap until E1 is closed.

Actor and audit

No public actor, audit, or correlation contract is published from OpenAPI alone.

Idempotency and retries

Retry behavior is documented conservatively because universal idempotency headers are not declared.

Topic	Status	Guidance
Current idempotency	No idempotency mechanism is declared.	Do not retry blindly. Check resource, status, batch, or job state before repeating the request.
Universal header	Not declared	Do not document universal Idempotency-Key support until OpenAPI and E3 evidence declare it.
Conflict behavior	Unresolved	Same-key changed-payload, in-flight retry, fingerprint scope, and TTL behavior remain endpoint-specific evidence gaps.

Async jobs and polling

Queued work is accepted work, not proof of completed workflow execution.

Topic	Status	Guidance
Immediate response	202	Treat the response as accepted or queued work, not completed workflow execution.
Polling and terminal states	Endpoint-specific	Use only operation-specific status endpoints visible in OpenAPI; generic job behavior, cancellation, retries, and retention are unresolved.
Later side effects	Possible	Queued work may later cause local or external effects only where endpoint evidence says so.

Files and artifacts

File-like routes need content-class, ownership, scanning, retention, and URL policy evidence before public recipes.

Topic	Status	Guidance
Content class	No file/artifact class inferred	OpenAPI text does not indicate file or artifact handling for this endpoint.
Ownership and storage keys	Not applicable unless a file field is present	Tenant ownership must be proven before retrieval or upload docs. Never expose storage keys as public identifiers.
URLs, scanning, and retention	Unresolved unless endpoint-specific evidence exists	Short-lived URLs, MIME limits, checksums, scanner status, retention, expiration, and legal hold behavior are not implied by OpenAPI examples.

Publication warnings

This endpoint needs explicit product, security/compliance, tenancy, or side-effect approval before publication.
HTTP 202 or queued behavior requires endpoint-specific polling, terminal-state, retry, and retention guidance.
Universal Idempotency-Key header support is not declared; retry only after checking endpoint-specific state.

Related platform rules

Workflow Guide Route Status Tenant Context Errors Rate Limits PHI and Security Publication Readiness Side-Effect Modes Idempotency Async Jobs

Evidence

Evidence	Status	Caveat
OpenAPI artifact	docs/openapi/openapi.json; OpenAPI 3.1.0; API 1.0.0.	Generated baseline contract only.
Route registry	Needs publication review from documentation classification overlay.	E6 route registry evidence is still required before external publication.
Example validation	Generated examples are internal baseline aids.	No external publication claim; examples must pass no-PHI/no-secret/no-raw-payload/no-storage-key checks.
Last reviewed	Implementation run 20260619T-docs-impl; source boardroom packet 20260619T064820Z.	Refresh this evidence for release workspaces.
Release evidence	E9 required.	No SDK readiness, production readiness, or expanded external docs claim from this endpoint page.

Payment Posting public API.

Payment Posting public APIs expose organization-scoped remittance visibility, payment posting record detail, local remittance metadata updates, local matching controls, dry-run staging, safe posting validation, payer-ID refresh previews, and finalization validation for Electronic Remittance Advice (ERA) workflows. The bearer API key selects the organization. Public callers should not send `organizationId` as a tenant selector. Read endpoints accept `payment-posting:read` or `payment-posting:write`; mutation and workflow endpoints require `payment-posting:write`. This public surface is intentionally conservative. Read responses return sanitized local QuickRCM records and omit patient demographics, raw X12 835 Electronic Data Interchange (EDI), payer payloads, transcripts, credentials, and storage object details. Workflow endpoints that return `externalRisk: SIMULATED_ONLY` should be documented as validation, dry-run, or safe queue simulation responses. They do not download Amazon Simple Storage Service (S3) objects, parse raw X12 835 payloads, create live queue work, post cash, mutate claim balances, deduct credits, or invoke Hash-based Message Authentication Code (HMAC) internal worker endpoints unless a future implementation changes the handler.

What this endpoint does

Use case

Use this when an integration wants QuickRCM to validate the shape and tenant ownership of proposed payment posting data before an internal or operator-controlled posting workflow.

Before calling

Authenticate with `payment-posting:write`, resolve `remittanceClaimId` from the same tenant, and send `validateOnly: true` unless intentionally testing queue simulation with `queueOnly: true`.

Request and response behavior

Request guidance

`claimChargeAmount`, `paymentAmount`, `patientResponsibility`, and `claimStatusCode` are required. `linePayments` and `adjustments` default to empty arrays. Each line payment requires `claimLineId` and non-negative `paidAmount`; each adjustment requires `groupCode`, `reasonCode`, and `amount`. At least one of `validateOnly` or `queueOnly` must be true.

Response semantics

HTTP 202 returns action `POST_PAYMENT`, mode `VALIDATE_ONLY` or `QUEUE_ONLY`, `externalRisk: SIMULATED_ONLY`, `accepted: true`, `queued: false`, and `remittanceClaimId`. It is not evidence of posted cash, claim-balance mutation, denial creation, patient balance creation, or credit deduction.

Errors and retries

Fix 400 validation failures, invalid amounts, missing required fields, or unsafe flag combinations before retrying. Treat 404 as missing or wrong-organization remittance claim. Use read-after-timeout before retrying because operator workflows may have changed local state.

Fix 400 validation failures, invalid amounts, missing required fields, or unsafe flag combinations before retrying. Treat 404 as missing or wrong-organization remittance claim. Use read-after-timeout before retrying because operator workflows may have changed local state.

Template boundary before examples

The route class, authentication state, tenancy rule, side-effect mode, idempotency status, async behavior, file policy, warnings, links, and evidence above are part of the endpoint contract. Treat generated examples below as internal baseline aids until release evidence closes.

Path parameters

Name	Location	Required	Type	Description	Validation and safety notes
remittanceClaimId	path	Yes	string	QuickRCM remittance-claim identifier in the path. It must belong to a remittance in the API key organization.	Minimum length: 1. Sensitive credential or storage-adjacent value; use placeholders only.

Query parameters

This endpoint does not define query parameters.

OpenAPI-declared header parameters

Standard platform header guidance appears in the governance panel. This table only lists operation-specific headers declared in OpenAPI.

This endpoint does not define operation-specific header parameters.

Request body

JSON fields from the generated OpenAPI schema with pilot enrichment applied where available. Nested object fields are shown with dotted paths.

Name	Location	Required	Type	Description	Validation and safety notes
validateOnly	body	No	boolean	Safe-mode flag that defaults to true. When true, response mode is VALIDATE_ONLY and no payment is created.	Default: true. Financial value; preserve decimal precision and avoid real account details.
queueOnly	body	No	boolean	Safe-mode flag for queue simulation. It defaults to false, and the current public response still returns `queued: false`.	Default: false.
claimChargeAmount	body	Yes	number	Required non-negative claim charge amount for validation, supplied as a JSON number.	Minimum value: 0. Financial value; preserve decimal precision and avoid real account details.
paymentAmount	body	Yes	number	Required non-negative proposed payment amount for validation, supplied as a JSON number.	Minimum value: 0. Financial value; preserve decimal precision and avoid real account details.
patientResponsibility	body	Yes	number	Required non-negative proposed patient responsibility amount for validation.	Minimum value: 0. Potential PHI; use synthetic examples and avoid logging raw values.
claimStatusCode	body	Yes	string	Required ERA claim status code string, capped at 16 characters.	Minimum length: 1. Maximum length: 16.
linePayments	body	No	object[]	Optional array of proposed line-level payment entries for validation.	Default: . Financial value; preserve decimal precision and avoid real account details.
linePayments[].claimLineId	body	Yes	string	QuickRCM claim-line identifier referenced by a proposed line payment.	Minimum length: 1. Financial value; preserve decimal precision and avoid real account details.
linePayments[].paidAmount	body	Yes	number	Non-negative proposed paid amount for a line payment.	Minimum value: 0. Financial value; preserve decimal precision and avoid real account details.
adjustments	body	No	object[]	Optional array of proposed claim-level adjustment entries for validation.	Default: .
adjustments[].groupCode	body	Yes	string	Adjustment group code such as CO, PR, OA, or PI; capped at 8 characters by the public schema.	Minimum length: 1. Maximum length: 8.
adjustments[].reasonCode	body	Yes	string	Adjustment reason code string capped at 16 characters.	Minimum length: 1. Maximum length: 16.
adjustments[].amount	body	Yes	number	Adjustment amount supplied as a JSON number. The schema allows positive or negative finite values.	Financial value; preserve decimal precision and avoid real account details.

Generated request example

Generated examples are baseline contract aids only. They are not external publication evidence and must not include real PHI, credentials, raw vendor payloads, raw EDI, transcripts, storage keys, or signed URLs.

{
  "claimChargeAmount": 125.5,
  "paymentAmount": 125.5,
  "patientResponsibility": 1.25,
  "claimStatusCode": "example-claimstatuscode",
  "validateOnly": true,
  "queueOnly": false,
  "linePayments": [],
  "adjustments": []
}

Successful responses

Generated response examples show the baseline OpenAPI contract. Tenant identifier echo, PHI redaction, pagination, money, date/time, and enum semantics remain endpoint-specific publication checks.

202

Post-payment request validated for safe simulation.

Generated from the OpenAPI response schema.

{
  "success": true,
  "data": {
    "action": "example-action",
    "mode": "example-mode",
    "externalRisk": "example-externalrisk"
  },
  "meta": {
    "organizationId": "00000000-0000-4000-8000-000000000001"
  }
}

Error responses

Errors must remain sanitized. Do not include raw payer, EHR, SFTP, SMTP, Stripe, LLM/OCR, browser automation, file, transcript, EDI, worker, or vendor payloads.

400

Invalid request.