LIVE OAK BANCSHARES, INC.: common-stock repurchase payments
Common-stock repurchase payments for LIVE OAK BANCSHARES, INC. Inspect selected reporting periods, original units and SEC filing links; download the financial history.
All LIVE OAK BANCSHARES, INC. financial histories
What this measure means
Cash paid to reacquire common stock during the period. This is not an authorization limit or a direct measure of the net change in share count.
Exact concept: us-gaap:PaymentsForRepurchaseOfCommonStock. Each value covers an annual-duration reporting interval, shown with both start and end dates. Different units remain separate; no currency conversion or interpolation is applied.
Coverage of this history
Selected reporting periods run from 2013-01-01 to 2015-12-31. The SEC response was captured on 2026-09-20.
This selected history ends more than two years before capture. Do not treat its final value as a current balance or current annual result. More recent filings may use another accounting tag; inspect the filings before drawing conclusions about the company.
Selected filing history
| Period start | Period end | Value | Unit | Filed | Source filing |
|---|---|---|---|---|---|
| 2015-01-01 | 2015-12-31 | 0 | USD | 2016-03-14 | 10-K · 0001462120-16-000016 |
| 2014-01-01 | 2014-12-31 | 0 | USD | 2016-03-14 | 10-K · 0001462120-16-000016 |
| 2013-01-01 | 2013-12-31 | 444,000 | USD | 2016-03-14 | 10-K · 0001462120-16-000016 |
Related financial histories
- LIVE OAK BANCSHARES, INC.: total assets
- LIVE OAK BANCSHARES, INC.: total liabilities
- LIVE OAK BANCSHARES, INC.: stockholders equity
- LIVE OAK BANCSHARES, INC.: net income or loss
- LIVE OAK BANCSHARES, INC.: operating cash flow
- LIVE OAK BANCSHARES, INC.: capital expenditure payments
- LIVE OAK BANCSHARES, INC.: financing cash flow
- LIVE OAK BANCSHARES, INC.: investing cash flow
- LIVE OAK BANCSHARES, INC.: retained earnings or deficit
- LIVE OAK BANCSHARES, INC.: basic weighted-average shares
- LIVE OAK BANCSHARES, INC.: diluted weighted-average shares
- LIVE OAK BANCSHARES, INC.: basic earnings per share
- LIVE OAK BANCSHARES, INC.: diluted earnings per share
- LIVE OAK BANCSHARES, INC.: income tax expense or benefit
- LIVE OAK BANCSHARES, INC.: net property, plant and equipment
- LIVE OAK BANCSHARES, INC.: interest expense
Inspect the source
- Entity
- LIVE OAK BANCSHARES, INC. / CIK 0001462120
- Captured
- 2026-09-20T09:06:20.580Z
- SEC response SHA-256
4193bc0ba5b6626b1b420417588ebb14223118fe2d7d44df3ec415212c440c0f
Current SEC company facts · Download the original response snapshot (gzip) · Download the selected JSON
Latest-filed annual-report facts per unit and reporting period at capture time. Duration facts cover 300 to 400 days. This selection can include restatements and is not a point-in-time backtest dataset. Missing concepts are omitted, never zero-filled. Values retain original units and are not currency converted. Extended concepts require compatible unit shapes and at least three reporting ends with changing values within one unit. Constant or incompatible added histories are omitted.
Public company accounting reference, not market prices, returns, an investment recommendation, or ALPHAC performance. Validate a separately constructed return series with the validation API; accounting values are not returns.
Use this in research
A financial period ends before its results become public. Use the filing date as a minimum availability boundary, inspect amendments, and retain the original filing vintage when testing historical signals. This latest-filed selection can contain information unavailable at the time.
These pages do not supply prices, total-return histories, corporate-action adjustments or a tradable universe. Build those inputs separately before evaluating a strategy. A profitable backtest can still reflect selection bias or costs that were left out.
Research methodology · Execution and cost assumptions · Check backtest overfitting
Build with the open-source tools
Use these accounting records as inspectable inputs. When you have constructed a return series, the validation tools can help test its statistical evidence and preserve the result with its limitations.
- Get an API key and run your first validation
- Connect the MCP server to your coding assistant
- Inspect the ALPHAC engine on GitHub
- Read the MCP server source and integration examples
Read the published dataset with Python
import json
from urllib.request import urlopen
with urlopen("https://canlicapital.com/company-data/0001462120.json") as response:
record = json.load(response)
print(record["fetched_at"])
print(record["policy"])
for concept in record["concepts"]:
print(concept["tag"], next(iter(concept["observations"])))