The graduation donation requirement, now end-to-end and with zero manual ops.

Many universities today operate "digital" processes that are really a chain of manual tasks: the student fills a form, makes a bank transfer, uploads a receipt, someone at the publisher reconciles the payment, someone else emails the file to the library, someone at the library uploads it into the catalog, and the registrar receives a confirmation email. publica.la automates that full cycle: integrated payment in local currency, direct delivery to the catalog via MARC/SSO/API, instant digital receipt, and real-time reporting for publisher and university. Zero recurring manual operation — that's why it scales with graduating cohorts without adding people on the operational side.

Yes, as long as the contractual framework between university and publisher establishes it clearly. The practice is standard across Latin America: the student pays for the copy, and that payment generates a donation receipt for the library. publica.la documents every transaction with full traceability for internal and tax audits.

Each country has its own rules. In Argentina we issue A or B invoices as applicable; in Mexico we generate CFDI with the donativos fiscal use (D04) or whatever the university specifies; in Colombia, Chile, Peru and Costa Rica we generate receipts according to local regulation. The publica.la team coordinates with the institution's tax area before launch.

The student already paid and the donation to the institutional catalog already happened: the title is loaded into the university's digital catalog. If for some reason the graduate drops out or delays graduation, that's a matter of their academic procedure, not of the donation program. The program does not contemplate automatic refunds for that reason, but refund policies are configured case by case at program activation with the institution.

In most cases, no. The standard integration uses SSO/SAML for authentication (compatible with the identity providers universities already use), MARC records for the bibliographic catalog, and IP-based authentication when needed. Activation takes 30 to 60 days from kickoff. If the university uses a specific ILS, the integration team validates compatibility in the first meeting.

The digital program coexists with the physical workflow — it does not forcefully replace it. Many universities run both channels in parallel during a transition phase. The difference is that the digital workflow is optional for the student (better experience, instant receipt) and mandatory in terms of institutional registration (each donation is registered in the digital catalog even when the copy entered in physical format).

It depends on the model. Two common schemes: (1) the publisher contracts publica.la and operates the program with allied universities — pays for the platform and shares revenue with the institution; or (2) the university contracts directly and coordinates with sector publishers to define the catalog. publica.la operates both models. In the first meeting we define which one fits best.

Let's talk. The six listed countries are where we have operational cases today, but the platform is built on top of Stripe, MercadoPago and PayU — that covers practically all of Latin America with local payment methods. If there's institutional demand in another country, we can activate it in a few weeks.