Skip to main content

Reviews

A review (BankReportReview) is the bank-side workflow for processing a published bank package. It captures who looked at the package, what they decided, and when. Each review is composed of section reviews — one per document area in the package — so you can approve part of a package while flagging another part for resubmission.

BankReportReview​

Top-level object representing one bank's review of one bank package.

Key fields

  • id.
  • state: BankReportReviewState — PENDING, PROVISIONALLY_APPROVED, APPROVED, or REJECTED.
  • reviewer: Employee — the bank employee handling the review.
  • createdDate, updatedDate.
  • provisionallyApprovedDate, approvedDate, rejectedDate — set as the review progresses through states.
  • bank — your bank, set automatically.
  • organization, bankReport — the customer and the package being reviewed.

The review aggregates a fixed set of section-review objects via named fields:

  • basicInformations: BankReportBasicInformationsReview
  • documents: BankReportDocumentsReview — wraps summaryReview, accountingReview, statutesReview.
  • authorizedSignatories: BankReportAuthorizedSignatoriesReview
  • businessVolume: BankReportBusinessVolumeReview
  • purpose: BankReportPurposeReview
  • generalAssembly: BankReportGeneralAssemblyReview
  • politicallyExposedPersons: BankReportPoliticallyExposedPersonsReview — also exposes hasPoliticallyExposedPersons.
  • boardMembers: BankReportBoardMembersReview
  • boardMemberAttorneys: BankReportBoardMemberAttorneysReview

BankReportSectionReview (interface)​

All the named section objects above implement the BankReportSectionReview interface, which exposes:

  • id.
  • bankReportReview: BankReportReview — backreference.
  • isReviewRequired: Boolean! — whether this section needs reviewing in this package (varies by configuration).
  • state: BankReportReviewSectionState — PENDING, PROVISIONALLY_APPROVED, APPROVED, or REJECTED.

reviewSectionById returns one section, scoped by the parent review's bank.

Two-stage approval​

The review state machine supports a provisional approval before the final approval — useful when a reviewer wants to signal "looks good, awaiting second pair of eyes" without committing the bank to a final decision. provisionallyApprovedDate is set on transition into the provisional state; approvedDate is set on the final approval.

Where to query​

  • Read: Querying reviews.
  • Mutations: reviews are produced by the bank-portal application, not by the External API. The External API exposes reviews read-only.